I’m trying to make multiple webhook requests run “sequentially”, not at the same time — but the “Wait” modules don’t seem to work properly (the flow keeps running in parallel).
Has anyone found a reliable way to queue or delay executions so that each webhook finishes before the next one starts?
Thanks in advance! 
Hello! Unfortunately, there is currently no mechanism in place to execute launches sequentially, one after another, upon the completion of the last one. All launches occur simultaneously as they are initiated.
This functionality is on our roadmap, but regrettably, it won’t be available in the coming months.
Of course, we could create a workaround by logging the order in the database and checking for triggers, but this would indeed be inconvenient and potentially slow.
Could you please share a specific case where this is important to you?
For example, in a spreadsheet with 100 records, two delete requests might be triggered almost simultaneously.
When the module performs a “Search Rows,” both executions detect the same positions (for instance, rows 98 and 100) before the deletion occurs.
However, once the first request deletes row 98, the second one tries to delete row 100 — which has now shifted to position 99 — and the scenario fails as a result.
The same issue occurs with other combinations, such as deleting rows 56 and 58 at nearly the same time. After row 56 is removed, row 59 shifts up to position 58, causing the second request to delete the wrong row (59 instead of the original 58).
You can try adding a queue system using the Data Store or Delay node. Store incoming webhook data and process them one by one with a scheduled trigger. The Wait node won’t stop parallel executions if multiple webhooks fire simultaneously.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.