Careful deploying to live after the scheduled maintenance, seems like they broke some things such as issue checker for backend workflows
been like that for a few weeks now - maybe a month or so
the issue tracker is unreliable to a high degree
if you delete fields or option values etc you really need to search BEFORE deleting them
often the issue tracker doesn’t register any issues until
1 - the workflow or page is opened in the editor
2 - the optimize application is run
3 - you go to push to live and then magically there are errors (this one is especially frustrating since the errors disappear each time you clear 1 but then reappear when you try to push live again… and you have to tediously clear each one in this “try to go live” loop)
I reported all these issues to bubble support several times but nothing seems to happen to fix them. I guess AI builders are more important.
Even searching the options doesn’t work. I searched all my option sets for every single option in the set, all came up not in use, so deleted it, ran optimize, refreshed app, see no issues, navigate to area where a now deleted option was actually in use and now the issue checker throws the issue.
This is pathetic Bubble, fix your issues that exist.
@fede.bubble any chance the team plans to fix these issues?
Same observation, and it has indeed been less and less reliable for some time. This is particularly true for custom events in BE.
When I contacted support, I was systematically told to make a video to show the problem. I had sent the same kind of screenshot as the one above. So gave up the support.
Field deletions are not always detected. Errors appear on deployment (and sometimes not)
So many basic functions that worked perfectly before, which is particularly frustrating.
This situation of issue checker and state of Bubble support has been like this for quite long. Not sure why you guys feel it is a last few weeks’ thing.
I have had this ideaboard item to have a manual issue checker button just like traditional coding has a “build/compile” option. That way they don’t have to keep running issue checker at every keystroke, and hence it can all be faster and optimal.
Yep - backend issue checker is soooo unreliable and lots of things don’t come up on the issue checker in the frontend until you actually go to the page or RE in the editor.
And things like deleted fields etc don’t come up in the issue checker either.
pairing this with a simple “run issue tracker” prompt when
- user navigates to a different page
- has made 100 changes since last run issue checker
the logic would be much more efficient and still achieve the same result of not having 1000 errors to sift through when you go to push live - which is why I imagine they do it in real time currently
I surfaced these issues to the team and they are investigating what’s going on with the issue checker. Thanks everyone!
This topic was automatically closed after 14 days. New replies are no longer allowed.