Looping Over Nodes Re-executes HTTP Request Each Time

Questions
, ,
1

Hey community,
I recently stumbled upon an issue while building my workflow. The problem is this: I want to loop over a series of nodes, and the first one is an HTTP Request node. However, every time the process moves to the next node within the same loop iteration, it re-triggers the HTTP node again.
I’m not sure if this is intentional by design, but it significantly slows down the entire workflow + introduces unexpected extra cost for the API usage. Has anyone else noticed a similar issue—or know how to resolve it?
Thanks!

2

Hi there @Asmerdis welcome to the community

, can you maybe share your workflow, does not need to be like the actual one, maybe just a split of the loop over nodes. n the http node

a screenshot of it executing would also be nice, anything visual that can help us understand your problem better

thank you

3

Thank you for your quick response. These is the nodes setup that i have.

[Loop]
↓
[HTTP]
↓
[Node 1] → [Node 2] → [Node 3] But it looks like that Node1 ,2,3 retriggers HTTP node only in the debug mode ( which is also very disorienting ) in the execution view, when I click the play button on any of these nodes.

4

from what i know, the triggering of a node, depends on how many items that goes into tht node

for example if before the http node, there’s 2 items, then the http node would get trigger twice

but if what you are saying that for example

there’s a

HTTP node → node A

and you manually execute node A, but it starts executing from the HTTP node and then goes to node A, i think that is somthn very normal n i come across it every time, to handle this, i would usually just pin the execution data of the HTTP node so it will not execute it more n more for testing

i hope this answer ur question

3 Likes