"You have unsaved changes" confirmation regularly shows despite having no edits

  1. My goal: Not see the dialog confirmation about unsaved changes if I don't have any.
  2. Issue: The "You have unsaved changes - are you sure you want to leave?" shows virtually always when I attempt to go from Edit -> View mode.
  3. Steps I've taken to troubleshoot: Checked "Compare changes". Tried in Chrome's Incognito mode.
  4. Additional info: (Cloud or Self-hosted, Screenshots)

The "You have unsaved changes - are you sure you want to leave?" dialog confirmation comes up almost always. This has been going on for months, maybe half a year, and I've just been too lazy to ticket it. (Also I was hopeful that it'd just get fixed on its own, but here we are!)

The issue? My app doesn't have any changes. I routinely check "Compare changes" and it says "No diff to preview."

It even happens if I open Edit mode directly from View mode and do nothing but go to Share -> View.

So I basically have to permanently ignore this warning, or take it at its word and check every time before leaving Edit mode. It's unfortunate that it's potentially a mix of false and true positives, but I feel like I have no way of knowing when/how to distinguish these cases.

v3.205.0-e4f696a (Build 249667)

1 Like

Hi @dguzzo,

Apologies for this inconvenience. The check for unsaved changes is a new feature that was implemented to ensure that app building progress was not being lost but it seems from your experience to be overly cautious.

Thank you for double checking that there are no changes from the "compare changes" page to ensure that this is a false warning.

I would love to help get this resolved and will be reaching out to the engineers that deployed this feature to see what questions they have and if they would want you to share an export of your app with us to investigate further.

I just tried leaving an unsaved change open when switching from edit to view mode via the play button in the top right and was surprised when I didn't get a warning.

I then self several unsaved changes open and switched from page 1 to page 2 and it gave me an 'unsaved changes' message where it included the names of the queries that were unsaved. So I am quite puzzled why your message is not giving additional details :thinking: are you on cloud or self hosted and if self hosted what version are you on?

Hi Jack, thanks for looking into this.

I've actually never seen that unsaved-changes dialog detail which queries have unsaved changes. It's always vague. Hmm...

I'm on cloud. The version number at the time was in my original post but here's the latest where the behavior is still occurring: v3.221.0-86cf90f (Build 255484)

(For some reason i thought the hosting type would be implicit in the version number, but maybe that was just a random assumption on my part! So i'll always try to include hosting type in addition to number.)

1 Like

Of course no problem!

I remember the first iteration of the notification was not specific, and then as of recently it was showing me query name, which is what led me to guess it might be an old buggy version but it seems that is not the case.

Given that you are on cloud your version will always be the most up to date so I will continue digging to see what could be the cause.

I just heard back from our app building eng team and it seems that this feature was previously owned by an engineer who left the company so we are working to track down the current owner now.

They said that the best thing for figuring out what is causing this would be for me to get a JSON export of the app along with steps to reproduce so we can test things out.

Thank you again for your patients on this!

Hi @dguzzo ,

A few more questions that will help us investigate --

  • Do you notice this issue after having made changes that you know have been saved, or just when you know you haven't made any changes?
  • Has this issue happened with the same frequency over the last 28 days (when you originally posted this message)? We rolled out a change in early June that I'd potentially expect to have made this warning less likely, especially in the scenario you described where you had just recently opened the app in editor mode.
  • When this happens again, can you check to see if you have this app open in multiple tabs?

Best,
Erin