"Unable to make changes" Error in AppSheet Editor that frequently causes loss of changes

[WillowMobileSys]

I have been seeing this error message (image below) for the past couple of months. It seemed to have stopped for a while but I am seeing it again this week.

I work as a co-author on a couple of apps and initially thought the errors were because the App Creators were making changes. But I have confirmed with the App Creators on several occasions that neither were making any app changes at the time I received the error messages.

The frustrating part is that I was losing the changes I had made. The only way to recover is to re-load the browser page and that seemed to prevent the recent changes from being saved. Has anyone else been experiencing the error message shown below?

Interestingly enough, today I get the error message but changes I just made ARE saved. Even so, it’s time to raise this problem to support.

Any other input by anyone?

[Marc_Dillon]

I saw this error several times earlier today. And same thing, the changes actually did save. I have NOT been seeing it for the last couple of months though.

[dbaum]

FWIW: I’ve seen this error a few times over many months, including once in the last couple weeks (although not today–I haven’t been editing apps today), and my changes have always been saved. This has always been for apps in my own account with no co-authors even enabled.

[Yogesh_laddha]

Same issue for me. I have been seeing this error message each time after I save. Even though the changes are saved, the banner is still there and need to refresh the app to remove it.

[Rifad]

@WillowMobileSys

Has anyone else been experiencing the error message shown below?

I was experiencing same issue and editor save was slow entire day.

This issue was there few months back and it was resolved.

[Marc_Dillon]

Same issue still happening today. I submitted a support ticket referencing this thread.

[Steve]

I get this every time I save. I engaged Support yesterday (case 2-5863000033754) but with no resolution. I was told my issue was transferred to a specialist and that I would get an update yesterday–which I did not.

Attn @devingu

[Steve]

I contacted Support again today to get an update. I was told that the issue was escalated to Engineering and that it is a “top priority”.

[Steve]

Received an email yesterday saying someone on the support team has accessed my account for troubleshooting. Progress?

[Steve]

The problem appears to be gone, though I’ve received no contact from Support. @devingu , should I expect Support to confirm my ticket was closed successfully?

[devingu]

Thanks Steve, we’ve actually escalated your ticket to the Eng team on Saturday.

We can close the ticket now if you don’t have the issue anymore, but feel free to reopen it if you encounter it again.

[Marc_Dillon]

Still happening for me this morning

[devingu]

We are escalating internally! thanks!

[WillowMobileSys]

Another occurrence this morning for me in an app I have not accessed in a while. It does not appear that I lost any changes.

[Steve]

I was mistaken, actually. The problem still occurs, but the error message no longer displays. I save changes and the editor reloads. If I then make any change, the Save button doesn’t light up, so I can’t save my changes. I have to reload the editor (and lose the changes!) to restore the Save button. I’ve already lost an hour of work this morning because of this.

Here’s how the ticket was closed:

I will respond to the email to say the problem is still there.

[devingu]

Hey Steve, noted!

Your ticket will be reopened. The product team is still actively investigating the issue.

[Steve]

Thank you. Here is the message I received:

[Steve]

The problem appears to be resolved for me, though I’ve received no confirmation from Support.

[devingu]

Yes.

The issue has been mitigated overtime by itself, still investigating from our side.

Edit: make some corrections

[devingu]

The issue has been mitigated overtime by itself, still investigating from our side.

Edit: make some corrections