I don't think this is entirely fixed. My team had a few apps that were having this issue intermittently last week, that seemed to have resolved. But today, we have one specific app where, when we open the editor, it does not display the error above, but it looks like everything has been deleted. No components, no code, and the diff tool actually shows everything being deleted, even though no changes have been made. This is happening to multiple people on my team.
Apologies for the issue, it seems that your issue is unrelated to the issue in this post but I can definitely try to help troubleshoot.
That is very odd and I don't think I have seen anything like that
On the bright side, the diff tool showing the changes should indicate that the app can be 'rolled back' to a previous version before this unusual un-triggered "delete everything" change was made.
We can do some further detective work if you are hosted on the cloud to see what request was made at the time of this delete event to see if we can pinpoint why this might have happened to fix any bug and make sure that it doesn't happen again.
If you are self hosted you would have the logs on your end to see more information about the delete event.
But also I am a little confused by the last screenshot saying that the app is fine so to confirm, in the editor everything disappeared and the change log confirms a deletion event occurred, however, when you switch from editing an empty app to viewing the live app, nothing is deleted and everything looks and works fine?
Hi Jack, thank you for the quick reply. Yes, that's exactly what we're observing, and yes, I agree it is confusing
We just tried reverting to the previous release, and that did fix the issue. Is it possible that some sort of automated migration went awry? We are hosted on the cloud: the version that we successfully rolled back to was published on January 28, and the only history entry since then was January 31, however as I noted, nothing was actually changed that day, that was when the problem started.
Glad to hear you were able to revert back and avoid any issues
That could definitely be possible, I am not super familiar with automated migrations but they should "fail gracefully" and give an error message but not change the current working version.
Good to hear you are on cloud, we should be able to pinpoint the time range when this happened and see the delete request, and hopefully get some answers from there.
Use that link to file a ticket and someone from our accounts support team will be able to do that in depth triage to make sure this doesn't happen again and that we make any fixed needed if there is a bug found