I have a whole workflow after this node, and generally I don’t think this workflow will be often used at the same time, however it could be a possibility of course.
My workflow is that data gets split up in batches → IF node → further workflow (let’s call it workflow ‘B’)
Now, just after the IF node, it will return to the split in batches node.
What happens if workflow B gets executed, all while another line of data is being put through the batch and the if node, which will also get into workflow B. In short: can workflow B handle two ‘runs’ at the same time?
thanks @Shirobachi ! So imagine you would have the flow above (1 to 8), but instead of a line going from 8 to 4, you have a line going from 6 back to batches (4).
I guess yours is best practice, right? but what would happen with what I described?
Example of an error:
It just stops processing. In this case the batchnode won’t get triggered anymore.
The reason here I am getting an error, is because of a timeout of 10s (yes, annoying), but it also does not give me the option to do a next step if there is an error.
thanks for your reply, that does make sense that it stops. In that case, perhaps you have a solution to trigger the next step if there is an error with a specific node (I saw there is an errornode trigger, but that would mean it triggers with any error, which would not be very helpful)
Thanks!
Also, you can set in node options to continue on error that would make that only that batch of items what make error would possibly do not run correctly, others would work completely fine (unless error ofc).
I would just suggest put right next some IF node what will check if error accrue and if do nothing (idk what you’re building but let’s say adding sth to DB, you probably do not want to add item with id undefined it could potentially break your other systems)
About error node, it’s trigger node what run completely separately, so it would be actually different to execution. That only for notifying you that error accrue, not handling it.
Pro-tip: make WF with error trigger node add, i.e. discord node, so it will let you know that error accrue. Go to settings and set this WF as error WF:
