Recursive Backend Workflow Stopped working

davi.mendes · 2025-03-05T10:39:50.384Z

Last update of our tool was Feb 24th, but on Feb 27th some Backend Workflows started becoming erratic, on Friday almost all of them not working properly. 5th Day of ticket opened for support, BUT without ANY support. Very frustrating, if it was something we did to ourselves we would be dealing with it, but for some reason Bubble stopped executing as it was executing before.

Just to clarify, the last update to Backend Workflows was more than a month ago, everything was working as per design, last Monday we did some cosmetic changes, and for 3 full days all was great.

Honestly the impact to the business is massive, I’m deeply frustrated with Bubble. I was an advocate of Bubble, but this is making be rethink it, difficult to digest that the tool stopped working as it was, without any modification from our end - it’s an unbearable risk.

I apologize in advance, but I’m frustrated after 5 full days of outage of my tool, and no reply from the support rather then “there are many support requests”.

johnny · 2025-03-05T10:44:45.654Z

Do you have recursion protection on?

davi.mendes · 2025-03-05T10:55:00.926Z

Thanks for the reply, but the workflows are running, but not working as they should and were working before.

They create the items, but most of data that once were being populated by the workflow is coming empty - and again, a week ago everything was working just fine and as per design, they stopped working for no reason as no new version of the tool was uploaded, that’s whats puzzling me.

retention-tech · 2025-03-05T14:28:35.861Z

I have the exact same issue, backend flow that has been working the same way since Aug last year and we noticed on Monday this week (3rd of March) that some data was not populated properly all of a sudden.

There must have been an update of some sort? I am going to log a bug ticket for this as well.

brandon10 · 2025-03-10T16:50:17.759Z

I also have this issue. I’m fairly new, so I assumed I just wasn’t doing something right on the new recursive workflow I was deploying. But, I just found out that the recursive backend workflow that had been working is no longer working. This basically kills an entire portion of my app.

My only other thought was that when I was debugging I triggered a spike in workflows. Then I cancelled all scheduled workflows. Perhaps Bubble changed some setting somewhere to disallow backend workflows to “save” my app from overloading work units (though it was nowhere close to actually using up my work units)?

I just did a simple test - with a very simple recursive backend workflow that should trigger itself every second indefinitely (don’t do this unless you are watching the log), and watched the log. It never triggered itself.

image592×333 15.4 KB

georgecollier · 2025-03-10T17:08:29.581Z

Check this setting isn’t too low @brandon10

CleanShot 2025-03-10 at 17.08.15@2x3024×616 73.3 KB

brandon10 · 2025-03-10T17:51:18.643Z

It is set to No Limit. Like davi.mendes’s initial post, the recursion had been working fine and only stopped working recently.

brandon10 · 2025-03-10T17:54:13.148Z

I submitted a ticket with a screen recording. Also have an issue with backend workflows not triggering APIs. (They trigger fine in regular front-end workflows).
Ticket ID
#247439

brandon10 · 2025-03-11T17:03:16.803Z

Turns out that my issue was that I had paused all tasks… Bubble, please make this more obvious (red or a warning sign or popup when you preview the app).