I am building a workflow to get news through RSS - however, running ‘Test Workflow’ brings me a 403 status code on the RSS Read node. But if I run the RSS Read module on its own it works just fine, not really sure why. It seems that when running test workflow it gets through all the RSS feeds and it decides to fail for no clear reason. I would appreciate to receive some wisdom on this
OK - So I found out that when running test workflow I am looping 286 items but when I run RSS Read I only loop 10 - not sure why that is the case though
Thank you for your insight. I was then using the Loop node incorrectly? I was going off of this tutorial here which had it set up like that:
But regarding the 403 I was kind of led to believe I had no access, however the test step button did not result in a 403 so I was a bit misled. Do you happen to know why the test step works and the test workflow doesn’t?
Perhaps I should rather use an HTTP request module instead of the RSS Read node so I an include a User-Agent header in order not to be blocked?
Update: I figured out it was the politico.com RSS that was being the problem
The loop node has a tricky behavior. The amount of input items should match the amount of the output items. Otherwise, it would be broken. However, in simple scenarios, you don’t need a loop node because any node can process multiple items.
Plus, it’s difficult to troubleshoot, as when you hit the test step button in any node inside the loop, you will test only the first iteration of the loop. To test the whole loops, you will need to click the test button on any node after the loop node (any node in the done branch)
