I’m creating a workflow for follow-up, and this workflow is supposed to perform a getCards in 9 Trello lists in parallel to send a message to one person from each list, and this was working fine! However, at some point, I saw the opportunity to configure it so that when one of the lists returns empty, it waits 5 minutes and runs the getCards of the next list again to send a message to a new person.
After configuring and testing the workflow, I realized that instead of running each getCards in parallel, the workflow was running the entire queue of one getCards before checking the getCards for the next list.
With that, my question is: will it always run this way, or is this a bug in the test? If it always runs like this, is there a way to work around it?
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
It is expected behaviour. If you have a set (list) of items n8n will process them sequentially, one by one, unles I misunderstood what you mean by “parallel”.