Backend Workflow errors are no longer visible in any of my Bubble applications and havenāt been for several days. Iām not alone in experiencing this issue. Bubble is actively investigating, and Iāve submitted a ticket awaiting their response.
Bubble fixed it (August 1). Must refresh your page to apply the change.
Yes, I noticed this. I had a client report to me they were unable to deploy to live due to 2 errors in backend workflows. When I went into the app editor to confirm, I saw no issues in issue checker. I focused and checked the box to run checks on the backend workflows, and saw the editor refresh, but after there were no issues shown. So I then went to the backend workflow tab, and nothing showed up. After that I refreshed the browser tab for the editor, but after refreshing nothing showed up still.
So I then went to deploy assuming the client fixed the issues, but that is when Bubble said can not deploy to live due two issues in backend workflows and with that the issue checker then showed two issues. Then I refreshed the browser again, and again nothing in the issue checker.
So yes, there is a problem with it. Unfortunately Iām not sure if anybody has reported it to Bubble or if they will fix it if it is reported to them.
Yes, just noticed this earlier a few hours ago. I had missing parameters that werenāt shown as missing.
Seems like all backend workflow issues are completely down.
Why do they deploy on a friday? Itās a known meme that you should never deploy on a fridayā¦
This began before Friday
Another thing I noticed is that errors arenāt showing up in the server logs, itās not just the issue checker.
update July 21: To see if you have errors in BackEnd Workflows, you need to do a LIVE deployment. Like this comment if you do. It may help to prioritize the problem.
update July 21 :
"After checking with the team, this is known behavior in Bubble-itās possible to see a clean Problem Checker when editing, so that problems appear later when browsing your application or trying to deploy. In some cases, these āhiddenā problems only become visible after interacting with certain pages or elements.
" In the meantime, we recommend that you browse your application and visit the relevant pages and elements after making any changes. This helps trigger the necessary background calculations that Bubble performs to flag up any problems. In larger applications in particular, these calculations may only detect certain problems once the specific page has been loaded.
We understand that this isnāt ideal, and rest assured that our team is looking at ways to improve this experience in the future. "
No, this is a new behavior, in which even when you do navigate to the backend workflows it doesnāt make these āhiddenā problems appearā¦but I do see how they have prefaced this with āin some casesā
Overall a very nice way for Bubble to say āwe know it is broken and we are not going to fix itā @randomanon how can they leave a broken thing unfixed?
The error checker no longer works if I create new WORKFLOW or CUSTOM EVENT APIsā¦ always in the BACKEND WORKFLOW section. Even a DEPLOY doesnāt work, so the LIVE has errors. A first in my case. 
Bubble Update: āI understand that we have had ongoing behavior where the problem checker has had trouble reporting errors in workflows when not on the page. However, I see that even when navigating to the page, a new unknown behavior with the problem checker occurs, as it did not report this expression as an error when visiting.ā
Is the bubble update, support replying that they now see the bug you reported as not the same as the āknown limitationā they previously brushed it off as? So that now they will escalate it?
Nonsense answer, backend workflows have nothing to do with āpages.ā The quality of support responses is extremely variable. Some of them are GPT 3.5 level hallucinations, others will actually go above and beyond to understand/troubleshoot the issue and talk with the engineers.
I think I experienced something similar: Errors ending up in Live version?
Yes, I saw your post and figured it is due to this same bugā¦seems sometimes the deploy to live will trigger the issues to appear while others it might get through and deployed to live. Very troubling that issues are deployed into Live
Bubble Update July 22: "I can confirm that this behavior occurs on my end and that it is unexpected that the problem checker does not report problems in backend workflows even when refreshing the page, setting the problem checker to check backend workflows, adding new actions with errors and updating expressions.
Iāve reported this behavior to our engineering team for their evaluation. They will look into this and actively work on a possible resolution. I apologize for the limited action I can provide for workarounds, but if these errors are no longer blocking your deployment application, we should be careful with the expressions we modify and make sure they are valid so we donāt break workflows."
PS: I communicate with Bubble in my native language, so any translation may not fully reflect the exact wording of Bubbleās technical team. If anything seems unclear, we can attribute it to translation discrepancies. @randomanon
OK, weird how theyāre treating this like any other bug rather than the Very Big Deal that it is.
Bugs are not big deals for bubble nowā¦big deals are UI updates, Mobile and fiddling with AI prompts.
Bubble just fixed the problem. Thank you. 
I just came in here to say that they didnāt. I am on version 29 (not version 30) if that makes any difference, although I doubt it would.
Edit: I clicked on the backend workflow tab and it updated with issues literally right after I posted thisā¦
Interesting, so it looks like their āfixā was to only refresh backend issues upon navigating to the tab. So you need to navigate away from and back to the backend workflows tab to have the issue checker update. This isnāt really a proper fix.
I do not know if it is fixed or not. My client project that had the issue which my client alerted me to, I had fixed the two issues when the deploy to live was clicked and showed needed to resolve two backend workflow issues not in the issue checker despite being on the backend workflows. After fixing them and deploying to live, my client next week attempted to deploy to live and same thing happened.
This time it was not the same two issues, that were resolved previously, it was two new ones that were deployed to live the week prior since the week prior the Bug was bigger than thought.
I have resolved the issues that were in the live app and deployed again, but there is absolutely no telling what other issues are in the live app.
