With the new default experience of a laggy and buggy editor, we can now expect a buggy and laggy experience with preview affecting our changes in preview mode…I’ve been noticing my tweaks, which editor seems to show as having saved, then refreshing my preview tab to get the new changes in place (black bar at top just changed indicator present) and I refresh, there is a very long and seemingly endless blue rotation indicating loaded, however, elements and data seem loaded, but changes are not affected, causing a belief the changes made did not resolve the issue, but in fact they did, it is just the laggy and buggy preview experience on refresh after changes in the editor.
1 Like
Yep some valid points raised.
Additionally I’d like to add a word of warning for the issue checker. It’s heck as buggy, both backend workflows and now frontend.
On the backend it will only register some issues, mainly high level on the actions and then inside actions it will simply ignore, even if you refresh the page and let the editor do its thing.
On the frontend, I’ve seen it intermittently miss errors/issues, it does catch after page refresh of the editor thankfully.
Still the backend can be the wild west at the moment and we’ve even seen bubble allowing pushing to live and these issues residing in production.
I’ve found its long been the case that many errors don’t register until the respective page/reuseable is loaded.
Though yesterday there were numerous backend errors that didn’t flag up until I actually went to deploy. Each time one was resolved it would clear them all, and not show them again until I attempted to deploy again.
1 Like
Has been an issue for about 4+ months now. Multiple bugs raised and ignored.
1 Like
Another thing we have recently seen is different expected results if the debugger is on or off in the frontend. This isn’t when we turn the debugger on and run workflows step by step, I know the results can be pretty off and already run, but this is more of page redirects and conditions via variables evaluating differently if the debugger is on or off.
For instance, there is a variable to check true/false if a user should be kicked back to the login page, with the debugger on, this works, with it off the user remains on the page. Another one we saw was that with the debugger on a process of doing x and then redirecting worked fine, with it off on the other hand, it would get caught and exhaust itself in a 301 redirect loop.
The “check backend workflows” checkbox always unticks itself for me. I don’t know why I would ever want this off, but I find it off pretty often.
This topic was automatically closed after 14 days. New replies are no longer allowed.