Recursive Backend Workflow running only the 1st iteration

Bugs
1

I’m facing a recurring issue with Bubble’s recursive Backend Workflows.
When I schedule a recursive workflow with just a few iterations (3–5), Bubble runs the first iteration only, but the following iterations are never executed.

Example:
I need to process a sale with 4 items. I schedule a recursive backend workflow passing the list and an index (iteration 1 → iteration 2 → iteration 3 → iteration 4).
Bubble repeatedly runs only iteration 1, and iterations 2–4 never trigger.

This is causing serious inconsistencies in my system (especially stock control).
Is anyone else experiencing this? Any insights on what might be causing it?

Edit: this happens rarely (once every >1.000), but it still impacts my client stock and revenue

2

Can you share a screenshot of your workflow actions?

3

I had recursive backend workflows erroring out, too. In the workflow, I had:

Run workflow - execute change to database - reschedule workflow for next item

If the database change errored out, the workflow stopped.

I changed the order of operations

Run workflow - reschedule for next iteration - make the change to database.

That way, if it errored out, it would still run. As my backend workflow ran every hour, any missed changes would be picked up at the next hour.

4

This topic was automatically closed after 14 days. New replies are no longer allowed.