Itâs âfixedâ insofar as it will show issues if you:
- switch back and forth between backend workflow and any other tab
- refresh the page
@randomanon @JohnMark This is NOT Fixed. I just had an issue. Iâm on the backend workflows, see 50+ issues. I resolve all. Issue checker shows no issues. I refresh browser page, upon loading again, still on backend workflow, now there are another 40 issues all on backend workflows.
So, even if we are on the backend workflows, the issue checker still doesnât show all issues on the backend workflows.
Seems at this point we will just be having to deal with this bug being part of the platform from here on out. @fede.bubble anything that can be done to get the team to look at this again? Iâve experienced it in two separate apps, both on version 30 since it was apparently âfixedâ.
Yeah itâs spotty. The most annoying/dangerous part is that it doesnât update live. Just today I had an expression that looked âcorrectâ instead of red despite being wrong. It only threw up an issue later after switching tabs.
Definitely not fixed.
checking with the team and taking a look at the JIRA tickets related to this
update: can I get an app ID or a bug report ticket from either of you @randomanon or @boston85719 ? Team is taking a look but it would be a lot faster if they could directly review with an app affected by these
@fede.bubble this bug is still persistent. Just had it happen in another app
Yeah, they still donât instantly update as the errors occur.
Iâve noticed the same issue. backend workflow errors donât show up in live mode, which makes testing really difficult. Refreshing the page helps temporarily, but I hope Bubble will fully fix this soon.
Had this happen this week whilst I was on vacation resulting in me having to taxi to a local library 2 miles away and spend 3 hours debugging and trying to figure out what/how had happened on some ancient machine with everything in Spanish since I wasnât able to change the PCâs language (nor keyboard settings for things like â@â which made logging in under duress moreâŚ..duressful).
A plugin update which had stated in the description that it was just marketing/description updates but in fact it turns out had removed a critical element (thanks Zerocode!) and so resulted in errors in reuseables which did not present in error checker. This then went into Live and caused utter chaos. It was only when the reuseables involved were opened in the editor that the errors then became apparent. It might therefore be that when plugin related errors occur, whatever logic Bubble typically employs for error checking doesnât trigger for plugin elements the same way it would for a typical error I.e invalid value in an expression, and so these are only picked up when the reuseable is loaded in the editor (Presumably some other functions run when this happens).
So highlighting this so either Bubble can look into it (doubtful) but more so to inform other users that if they update plugins, it might be an idea to load up any pages/reuseables where that plugin is used to ensure that nothing is amiss before sending it down the wire.
Also donât believe plugin update descriptions - test any relevant workflows/actions, even if they say they have just updated the description.
You can either refresh the page or switch from backend to regular workflow tab and back. But yeah, this needs to be fixed.
Neither of these work. Iâve had continued experience where despite being on the backend workflow tab, despite refreshing the browser, there are still times it doesnât pick up the issues until you attempt to deploy to live, and even then it doesnât always spot them and still might let issues be deployed to live.
This issue needs serious focus on Bubble side. It has been 29 Days since this post and more than 31 days since it first started. @fede.bubble
I donât speak for Bubble but I know updates are coming around here - they made an editor update on the logic that also deals with the issue checker last week but rolled it back because it created a few more bugs. So, its definitely on their radar and may be patched with that soon (along with much faster editor load times etc)
Yeah but the fact that you even have to start your posts like this means you kinda effectively do. 
no I just know from a support ticket 