Skip to main content
Rollback restores a previous successful deployment as the live state without re-running the original deployment workflow.

​
How rollback works

When you roll back to a previous deployment:
  1. The target deployment snapshot is applied to the tool.
  2. The search index is updated with that snapshot.
  3. The current live deployment pointer is moved to the selected deployment.
The tool slug stays the same during rollback.

​
When rollback is allowed

Only deployments that meet all of these conditions can be rolled back:
  • Status is success
  • The deployment is not already the current live deployment
  • No deployment is currently running for the same tool
Failed, canceled, and in-progress deployments cannot be rolled back.

​
Start a rollback

You can trigger rollback from either place:
  • Deployments table: Open the row menu and choose Rollback to this deployment
  • Deployment details page: Click Rollback to this deployment
Both flows show a confirmation dialog before the rollback starts.

​
Why rollback can be blocked

Rollback is blocked when another deployment for the same tool is pending, queued, or executing. A running deployment could overwrite the rollback when it completes. If that happens, wait for the deployment to finish or cancel it before retrying the rollback.

​
Edge cases

  • No current deployment: Rollback still works and creates a new current deployment pointer.
  • Tool has no slug: Rollback fails with a clear error.
  • Concurrent rollback: Last write wins.

​
Verify the result

After the rollback:
  1. Open the tool’s live page.
  2. Confirm the expected metadata and content are visible.
  3. Check search results if discoverability changed in the rolled-back version.