Notifications
Clear all
Topic starter
I'm encountering issues with workflows that involve nested loops. Specifically, the inner loop seems to have a problem because it marks all incoming inputs as completed before iterating through them. I've tried using the 'reset' functionality, but it doesn't resolve the problem. It only processes the first input, and all subsequent inputs are bypassed.
- Version 1.21.1
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via callin.io cloud
- Windows
Posted : 29/02/2024 5:33 am
It seems your topic is missing some crucial details. Could you please provide the following information, if it applies:
- callin.io version:
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via (Docker, npm, callin.io cloud, desktop app):
- Operating system:
Please provide the requested details.
Posted : 29/02/2024 5:33 am
Hi Bhojraj, welcome to the community!
Could you please share your workflow here so we can take a look at it? Just click the ‘
Posted : 29/02/2024 7:27 am
Topic starter
Posted : 29/02/2024 8:36 am
I'm encountering the same issue. I've reported this problem on GitHub
8764
Posted : 29/02/2024 10:19 am
Hello,
Looping within a loop can indeed be challenging. It appears you've made progress by looping back from the order table, but there are a couple of points to consider. The primary loop might execute more times than anticipated because the 'If' branch is looping back, in addition to the Airtable node.
Observe the example below:
The upper section will execute the initial loop node six times (once for each input plus one for the completion output). However, the lower branch, which proceeds from the 'If' node to the loop as you've configured it, runs nine times. This is due to the output from 'Replace Me 2' plus the output from the false branch, plus one for the completion output.
Regarding the other aspect, where the loop outputs data to 'done' instantly, this is likely due to multiple executions feeding into the node, as demonstrated in the example workflow. It's generally not recommended to use nested loops in this manner, as it can lead to complications. A more effective approach is to utilize a sub-workflow. In this scenario, you would move the second loop into its own separate workflow, then call that sub-workflow, eliminating the need to loop back to it.
Posted : 29/02/2024 1:24 pm
Good news, this may be resolved shortly with this PR: feat(Loop Over Items (Split in Batches) Node): support multiple runs by elsmr · Pull Request #8777 · n8n-io/n8n · GitHub
Posted : 29/02/2024 4:11 pm
This thread was automatically closed 90 days following the last response. New replies are no longer permitted.
Posted : 29/05/2024 4:11 pm