Hey, second time encountering this. Is there anyway to prevent this or roll this instance back? Yeah, having backups would be a start 
Just wondering what I can do when facing this situation. Thanks 
To add, I have a js function associated with these buttons that do look at the document.head â this is intended to actually look at this documentâs head. Could be an issue.
Just wanted to follow back up and see if anyone from WeWeb could shine some light on this or help me prevent these issues in the future.
Hi @Cam 
Best thing to do is report the bug here with information about what element was there before.
Not 100% rolling back to a previous version of the editor would work but you can give it a try by going in your project settings in the Deployments or Backups tab.
Here are the docs on the topic.
Could be. Have you tried removing it or opening the project in safe mode?
Hi Joyce, Iâll have to try this in the future! I had removed the div already with the components that had the js added to them. Thanks so much for this information, itâs super helpful.
Ah yes. Unfortunately, thatâs the one thing that will make it impossible to recover the element 
The tech team is working hard to get rid of those undefined elements but the fix may still be a few weeks ahead. In the meantime, weâre going to change the âELEM UNDEFâ message so itâs less scary and more informative by guiding you through the recovery process.
This has happened to me twice and because it is happening to multi page sections it is messing up a ton of my work, and although it says click here for more info (see screenshot) you cannot actually click anywhere for more info.
I donât understand why the free tier doesnât have the capability to save because then I could roll back to the previous iteration. It would be nice to understand why this is happening so we know how to avoid it.
Hello @Joyce seems like either the commits donât work, or it doesnât work with the Libraries, I can see my broken component working in the last Automatic Commit, but when I do a rollback, it seems like it does nothing.
I am also having the same problem, but with whole pages. All my elements stopped working.
Did the weweb support solved the issues for you all?
I submitted a support ticket yesterday, but the response from WeWeb support has been very slow. This is a critical problemâmy users are complaining that they canât use the app properly, and itâs impacting their experience.
Iâm starting to lose confidence in WeWeb as a reliable no-code platform. If the support remains unresponsive and the platform continues to cause bugs in my production app, I might need to reconsider using it.