Backend Workflow bug

Hello Bubble community,

I’m reaching out in a state of unprecedented frustration and urgency. My office complex management application, which is critical to my income, has been experiencing severe issues for the past 5 days. The main backend workflows, which are essential to the app’s functionality, are completely non-operational.

The problem began last Saturday when I discovered and immediately halted an infinite loop in one of the backend workflows. However, the aftermath has been catastrophic - almost all backend workflows ceased to function properly. I attempted to restore the application to a version from weeks ago, but the issue persists.

I’ve been in constant communication with Bubble support, opening multiple tickets, but after 5 days, my app remains disabled. This downtime is causing me to lose customers and is severely impacting my business.

The most frustrating part is that Bubble support has not been able to provide a solution. They’ve indicated there’s a server-side issue but are unwilling or unable to restore or reset the servers for my application.

I’m at my wit’s end and feeling utterly helpless. My livelihood depends on this application, and every day it’s down, I’m losing more business.

I would greatly appreciate any suggestions or advice from the community. Has anyone experienced a similar situation? How did you resolve it? Are there any workarounds or alternative solutions I could try?

Thank you in advance for any help or insights you can provide. I’m desperate for a resolution and open to any ideas.

1 Like

There’s no possible answer because there’s no detail about your issue. What was causing the loop? What did you do to “halted” the loop? When you revert to a previous version, what is now the issue your are facing?

1 Like

The loop was created in my attempt to create a workflow that transfers my data to the mysql server - it is not related to the backend workflow that was affected except that it was also a backend workflow

And regarding the after-restore version - the problem remains the same problem - backend workflows simply do not work when scheduled, this has always been the problem

Have you unpaused the workflow scheduler?

2 Likes

I paused and then resumed several times - not worked :confused:

Can you first do a test: pause the scheduler. Trigger the WF to be scheduled. Inspect the scheduler to see if the scheduled WF is there. It will help to know if the problem is when you schedule the action or when the backend WF run.

3 Likes

I did other tests - from the tests that I and the support team also tried

The problem is in the backend workflow itself and not on the “frontend” side - they have been claiming for 5 days that they are investigating this and there is no solution

The frustration of not being prioritized is a real bug on their side

Unfortunately, I have no contact with anyone senior in the company to try to push and prioritize this problem - I would appreciate it if someone knew how to refer this problem to the relevant parties because I am having a lot of difficulty with the support who also seems to be having difficulty with this bug

I am not offered even a temporary solution that will allow me and my customers to continue using the product that I built for two years

What logs said once the WF run? Is it running?

I’ve never heard about this kind of issue before.

The only person here that could help you, maybe, is @fede.bubble I think.

Continue to force support to escalate your issue. But honestly, not sure actually there’s a real bug for your case… and this may be why you didn’t get an answer or a fix already…

The only thing I can suggest, if other backend WF are running, is to create a new version of your workflow (don’t duplicate it, create it from scratch).

2 Likes

Look, the thing is that the application worked perfectly a week ago, I restored the application dozens of times and again restoration did not work… It seems that something there is broken

I tried to strengthen the workflows and maybe try to delete steps or rearrange them - didn’t work

I haven’t tried to recreate them yet - the thing is there are a lot of them and it will take a lot of time and work

I’m sure the problem is on the server side - I just feel that the people handling my application at the moment are simply not the most professional in the company who can help me and it’s a shame

It’s really something serious that is probably big on them

@fede.bubble I would appreciate your help and guidance to professional and good factors

Do this, and we will help.

Restoring the application would have no effect on backend workflows/scheduler anyway, so I’m not sure what the point of that would be.

1 Like


I didn’t quite understand what should be done - but here is a screenshot of a screenshot after I paused and then clicked “show” if that means anything to you

@georgecollier

Click ‘resume tasks’


done

what now?

What is the workflow that you tried to schedule? Does it appear there?

Okay, well your next workflow is scheduled for 2:00am your time, so it’ll run in 20 minutes.

If you’re not seeing workflows, you need to schedule them.

1 Like

I didn’t quite understand what you were saying

But let’s say you said that a workflow should be scheduled in 20 minutes, right? So the problem is that it just won’t run because of the bug…

Cool, in 20 minutes, show us the log entries for 1:59am-2:01am.

2 Likes

Now I checked and this specific order has been deleted

But I understood what you want to see - I will now do something that will show you before and after

Also, share your backend WF settings, step, conditionnal.
Do you have privacy rules on your DB that could affect the WF?..

1 Like