# Recursive Backend Workflow running only the 1st iteration

**URL:** <https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736>\
**Category:** Bugs\
**Created:** [November 19, 2025, 7:47pm UTC](https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736 "2025-11-19T19:47:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaopaulorramiresp](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@joaopaulorramiresp](https://forum.bubble.io/u/joaopaulorramiresp)\
**Post date:** [November 19, 2025, 7:47pm UTC](https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736/1 "2025-11-19T19:47:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![mubaraqishola23](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@mubaraqishola23](https://forum.bubble.io/u/mubaraqishola23)\
**Post date:** [November 19, 2025, 9:52pm UTC](https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736/2 "2025-11-19T21:52:24Z")

</div>

Can you share a screenshot of your workflow actions?

---

<div class="post-metadata">

**Author:** ![jeffrey.j.obrien](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jeffrey.j.obrien/32/76654_2.png) [@jeffrey.j.obrien](https://forum.bubble.io/u/jeffrey.j.obrien)\
**Post date:** [November 21, 2025, 8:05pm UTC](https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736/3 "2025-11-21T20:05:03Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [December 3, 2025, 7:48pm UTC](https://forum.bubble.io/t/recursive-backend-workflow-running-only-the-1st-iteration/385736/4 "2025-12-03T19:48:05Z")

</div>

Closed on December 3, 2025, 7:48pm UTC

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