Command Palette

Search for a command to run...

Roll back a deploy

Revert an instance to a previous deploy from the project home.

Every successful deploy is recoverable. If a release breaks production or introduces a regression you spotted in the wild, you can return the instance to a prior deploy without re-running an AI session or copy-pasting old code.

Where rollback lives#

Project home (/p/<id>) → the row for the instance → action menu → Rollback.

How to roll back#

  1. Open the project

    Workspace dashboard → click the project. You land on the project home.

  2. Find the instance row

    The Instances table shows every connected environment. Locate the one you need to revert.

  3. Open the action menu

    Click the row's action menu. Options: Deploy here, Promote to next instance, Deploy history, Rollback.

  4. Pick a target

    Rollback opens a list of recent deploys. Each entry shows the version (e.g. v17), commit message, author, and date. Pick the one to revert to.

  5. Confirm

    Studio re-runs the same CloudShell deploy job that originally shipped that version. The instance lands back on the older code; the in-Studio editor still holds the current branch state, so you can keep iterating.

What rollback does and doesn't change#

  • Does put the deployed instance on the older code. The instance URL serves the rolled-back version immediately.
  • Doesn't touch your GitHub repo's HEAD. The newer commits stay in history; nothing is rewritten or deleted.
  • Doesn't touch in-progress Studio sessions. Anyone editing in the browser keeps editing the same branch state.
  • Does create a new entry in the project's Activity feed and a notification for everyone subscribed to rollbacks.

Inspecting deploy history#

Same action menu, Deploy history. Lists every deploy to that instance with version, commit, author, status, and date. Useful before you roll back — pick the version that was last known good.

Common questions#

Can I roll back an in-progress deploy? No. Wait for the deploy to finish or fail; rolling back over an active deploy isn't supported.

Can I roll back to a deploy older than the last 50? Yes — Deploy history goes further back than the rollback picker shows on first open. Scroll for older entries.

Can I roll back a Migration project's initial build? No, the initial Migrate-on-ramp build is the floor. Subsequent deploys roll back as normal.