My Application Only Works in Debug Mode O.o

Kind of wild, but true.

I keep experiencing very hard to trouble shoot issues and bugs, workflows running incorrectly, Custom States populating incorrectly…

So naturally I turn on Debug mode to troubleshoot the issue…

The problem is none of the issues appear in Debug_Mode. It’s only when debug mode = false that the bugs appear.

Has anyone experience this before? I submitted a bug report to bubble already, just wondering if I’m nuts.

1 Like

I’m curious, please do share an example of a workflow.

Just to be sure - don’t you use isn't live version in your WFs conditions?

I don’t.

Here’s a video demonstrating the issue. It’s what I sent to bubble via bug report: Loom | Free Screen & Video Recording Software | Loom

That’s creepy indeed. My 2 hunches:

  • open the browser console to see if any errors are showing up when it loads
  • is there a rogue set state action in that page somewhere?

Same issue here, I have strictly no idea where it comes from.

Did you find out the solution @ian11 ?

1 Like

Hey @louis2 - here is what happened from Bubble support…

  1. The found the reason I was having an issue with my app (The issue I was trying to troubleshoot with debug mode) It was a workflow thing…
  2. When I asked why I couldn’t troubleshoot it myself in Debug mode, here is the answer that they gave me:

The debug mode runs each action step by step and does not always wait for the completion of each action before itself due to the different execution rules, which is why the behavior might slightly differ at times.

I was able to isolate the workflow that caused this by working on a local copy and disabling each workflow that had to do with the ‘zero scored category’ custom state until I found the error no longer reproduced. It looks like the custom event is being triggered at a point in run mode which is causing the state to get populated.


If it’s at all helpful (in case you have a similar set up) my issue was stemming from a Workflow set to “Trigger when”

3 Likes

Many thanks for your reply @ian11, I might have found the workflow that causes the issue. It seems to be a Workflow Do Y Only When custom state = X and I’m looping over it.

But it get stucked at the first iteration in run mode

I need to test an alternate way to achieve this easily.

Thanks again for your detailed reply :pray:

Yes, That’s exactly what was happening with mine.

I’ve found a (very weird) way to solve it.

I simply put the yes/no custom states (that indicates if the script has to loop again) visible in a text element in the app. Set it to 1x1px to make it invisible for the user. And it works…

Thanks again @ian11 for having helped me on this

1 Like