App Builder repeatedly resets project to FETCH_HEAD and removes previously committed changes

Teable Discussions
1

Hi everyone,

I’m running into a serious persistence issue with App Builder and wanted to check whether anyone else has experienced this.

I’ve been working on an application over several sessions, making fairly substantial changes. The changes are implemented, tested successfully in the preview, and committed locally by App Builder.

However, the App Builder sandbox keeps restarting/resetting and previously completed work disappears.

The Git reflog shows entries such as:

reset: moving to FETCH_HEAD

After one of these resets, the active branch is replaced by what appears to be a platform baseline version of the project, while the commits created during the previous session are no longer part of the active branch.

For example, App Builder confirmed that:

  • Changes had been implemented and tested successfully.
  • The changes were committed locally.
  • Shortly afterwards, the sandbox restarted.
  • The workspace was reset to the platform baseline.
  • Previously implemented features disappeared.
  • App Builder then had to reconstruct some of the lost functionality manually.

This has now happened multiple times.

During the investigation, App Builder also reported that git remote -v is empty, meaning the commits it creates appear to exist only inside the sandbox. Some previous commits initially remained as dangling Git objects, but later several of the older implementation snapshots were no longer recoverable.

The latest recovered version is currently committed again locally, but App Builder itself warns that another sandbox reset could remove it again.

So my questions are:

  1. Is this expected App Builder behavior?
  2. What exactly is FETCH_HEAD pointing to when the workspace is recreated?
  3. Where is the persistent/canonical project source stored?
  4. Why aren’t commits created by App Builder becoming part of that persistent project state?
  5. Is there a supported way to make the current source state durable across sandbox restarts?
  6. Should App Builder normally have a Git remote configured automatically, or is an external repository required?
  7. Is there any way to prevent App Builder from resetting a project to an older platform snapshot?

The concerning part is that this isn’t just uncommitted work disappearing. App Builder explicitly commits and verifies the changes, but those commits can still be lost when the environment resets.

Has anyone experienced this, or is there a recommended way to make App Builder project changes persist reliably across sandbox restarts?

2

Hi @Alex ,

Sorry about the lost work, and thanks for the detailed report.

Could you share the App ID of the affected app? You can find it in the app’s URL (it looks like appXXXXXXXXXXXX). A rough time window of when the resets happened would also help.

1 Like
3

@Leo - app6XlkrT0gevYkLvNe. Resets happened yesterday around midnight CET and today first half of the day CET. Now, 3PM CET - I think most (but not all) of it was restored after some back and forth with cuppy, but again, moving forward - I’d like to understand how to prevent losses. Thank you!

4

Hi @Alex ,

Thanks for your feedback. We’re looking into this now. As an immediate step, we’ve applied a manual fix, but this is only a temporary workaround, not a permanent solution. We don’t have a fix in place yet, but we’re treating this as a priority and will work on getting it properly resolved.

1 Like