Hello.
I have a simple workflow - take data from the database and push rows to customer.io.
The only thing in response what I’m interested in is - request returns 200 (success) I’d love to add something like this:
queries with multiple workers - now it’s run in parallel and each request waits for a response and then runs next - with my number of data it’s taking few hours to run. Would be great to speed it up for example by adding threading - how to do this?
if any of the response fails then pass request params to the next node which will save to file
I’ve tried split in batches with for example size of 10 and duplicate customer.io node, but each node receives same data. I’d like to send different packs of records between nodes. Is this possible?
In the node, go to the Settings tab and toggle Continue On Fail to true. This will execute the workflow on failure. You can then check with an IF node if the previous node had any failures and design your workflow accordingly.
Can you also share your workflow (select the nodes and copy them and paste it here)? This would help me understand your issues better and help me replicate it.
This Is my code. And the problem is that I have only one CustomerIO which is updating data. I’d love to split rows to multiple CustomerIO workers and push different batch to each of them
@Kacper thanks for sharing the workflow. I now have a much better understanding of your question. The nodes in n8n can’t execute in parallel. Only after one node has finished it’s execution the next is executed. Hence, splitting the data and sending them to different CustomerIO node will not help.
One solution that is on the top my head is to create multiple such workflows and query limited data in each of them. This is not an ideal solution though.
If you want to take this route, you can programmatically set the value of the workflow ID. Assuming that the workflows are saved consecutively, they will have an incremental ID. For example, 1, 2, 3, and so on.
