What happens if a user closes an embedded AppSheet app while it’s still syncing?

AppSheet AppSheet Q&A
1

Hello everyone,
I’m embedding my AppSheet app inside a website using an iframe. I have a question about the sync behavior.

If a user submits a form and AppSheet starts syncing, but the user closes the webpage before the sync is completed, what exactly happens?

  • Are the unsynced changes lost permanently?
  • Does AppSheet retry the sync later, or is the session fully terminated?
  • Is there any way to ensure that pending data is saved even if the user leaves the page?

I want to understand the exact behavior so I can guide users properly and avoid data loss.
Thanks in advance for your help!

1 Like
2

I’ve never embedded an app in an iframe, so I can only speculate.

I’d expect not, though it depends on how you’ve embedded the app. I’d expect unsynced changes to be saved in the browser until the embedded app is opened again, at which point I’d expect the sync to resume. This would be very easy for you to test. Very, very easy. Trivial, even. Have you tried?

See above.

No.

See also:

3 Likes
3

This is my experience.

2 Likes
4

Hey,

Hope you’re keeping well.

When an AppSheet app is embedded in an iframe, syncing is handled entirely within the browser session. If the user closes the page before the sync finishes, the pending changes are discarded because the local app state is lost, and AppSheet will not retry later without that session. To avoid data loss, you can enable Delayed Sync or Automatic Sync in the app settings so submissions are pushed immediately before the user navigates away, and design forms to save data on each change rather than only at the end. You can also consider breaking longer workflows into smaller saved steps so each commit happens before the user exits.

Thanks and regards,
Taz