Ensure Recursive Workflows Run in Sequence

[mike35]

I’m creating a process where I’m using a recursive workflow to create a set of items. For a few reasons, I want to make sure that each item is created before the next one is added. One reason is that I need to check a running total to make sure that the batch doesn’t exceed the total.

Is there a way to ensure that a recursive workflow completes before running the next loop? I’ve added a second delay before kicking off the next workflow, but it doesn’t seem to be foolproof as sometimes I can tell the next iteration starts before the previous one was complete.

Or is there a better way to generate a set of items aside from using a recursive workflow?

[cmarchan]

Hello @mike35

On the rescheduling action apply a condition where the creation step needs to be not empty

[mike35]

Thanks for the help, @cmarchan. That doesn’t seem to work. I think it’s because I’m calling another backend workflow that performs multiple actions. The backend workflows run asyncronously, so the next steps won’t wait, right?

[cmarchan]

Hello @mike35

Explore custom events. This helps with order of operations.

This post should help shed some light on this topic:

Tip: Order of Operation

Hey there, thanks for posting! If you’re interested in Order of Operations, you might check out this section of our Custom States tutorial: How to Use Custom States | Bubble Tutorial - YouTube Then, here is some information about Bubble workflow logic: For efficiency purposes, workflows run in parallel across the server and the front end. Despite the names “Step 1”, “Step 2”, it is important to note that a given step does not necessarily wait for the previous one to complete before triggering …

[mike35]

Thanks - however custom events can only take in one object as a parameter, correct? This is a limitation I’ll need to work around.