Skip to main content

​
Versions and rollback

Your app blueprint is versioned. End users keep seeing the last published blueprint until you ship draft changes. New apps start with an Initial version already published (an empty scaffold), so guest and portal surfaces always follow a published pointer while you build in draft. Version history covers the blueprint (tools, pages, data structure, and related settings), not every row of customer data in a project. Field definitions under App Settings are part of the blueprint: guests and the published portal use the last published fields. Stored values stay live. When the draft differs from what customers see, a banner appears at the top of the builder with a Publish button. Use that to make the draft live. You do not need to open the Publish page first. Sidebar Publish (next to Preview) is for history, change lists, rollback, and forks.
Publish the current draft after Access review looks clean for dispatcher and requester.
Restore my draft from last Thursday’s snapshot; do not change what customers see until I publish.
After Publish or Show customers this, Preview as a customer role on Published. After Restore draft, customers still see the previous published version until you Publish again. Use View changes on the banner or a history row before you promote anything risky.

​
Publish vs Restore draft vs Show customers this

These are three different actions on the Publish page: Use View changes on the banner (or the Publish status card) to compare the live draft to what is published. Use View changes on a history row to compare that snapshot to the previous complete snapshot.

​
Open snapshot (Publish paused)

Publish is paused while a build is still open (for example a Building turn in progress). The banner and Publish page show that Publish is blocked and when that open build started. If the build finished but Publish stays blocked:
  1. Open sidebar Publish.
  2. Choose Finalize open snapshot.
  3. Confirm. This completes every open snapshot as Auto history entries and unlocks Publish. It does not change what customers see.
If several failed builds left stacked open snapshots, one Finalize closes all of them. Abandoned open snapshots are also cleared automatically after about two hours of inactivity so Publish cannot stay stuck forever.

​
Limits

  • Finalize open snapshot requires an admin (or owner) role on the app.
  • Draft forks are discarded automatically when you publish.
  • Restore draft (and chat Revert) ask for a fresh authenticator code. If you have not set one up, the dialog says Authenticator required and Open Profile takes you there.