App Deployment History and Rollback

Published · Last updated: May 2026 · 2 min read

Who this is for

Users who want to review past deployments for an app, understand what changed, or roll back to a previous working version.

How to View Deployment History

Open the app detail.
Click the Deployments tab.
The last 50 deployments are shown in reverse chronological order.

Each deployment entry shows:

Date and time of the deployment
Commit SHA (for git-source apps) or image tag (for container apps)
Triggered by (user or webhook)
Status (succeeded / failed)

How to Roll Back a Container App

For apps deployed from a Docker image (source: docker):

In the Deployments tab, find the deployment you want to roll back to.
Click Rollback to this version.
Confirm.

CloudAIPilot re-runs the deploy with the image tag from that deployment. The audit log records this as app.deploy.rollback.

Alternatively, use the commit picker to manually specify an image tag:

Click Deploy → Advanced Options → Image tag → enter the tag.

Note: Compose apps do not support rollback by image tag. Roll back compose apps by redeploying from a previous git commit or reverting your docker-compose.yml in git.

How to Roll Back a Git-Source App

For apps built from git (source: git):

In the Deployments tab, find the commit SHA you want to roll back to.
Click Rollback to this version (or copy the SHA).
If using the button: CloudAIPilot re-deploys with gitRef set to that commit.
If using the commit picker: click Deploy → Advanced Options → enter the SHA in Git ref.

Re-running a Failed Deployment

If a deployment failed partway through:

Find it in the Deployments tab.
Click Retry to re-trigger the same configuration.

What Success Looks Like

The rollback deploy completes. The app's commitSha or imageRef updates to the rolled-back version. The Activity Center shows the deploy as completed.

Common Issues and Fixes

Issue	Likely cause	Fix
Rollback button missing	Compose app (not supported)	For compose: revert in git and redeploy, or update compose YAML.
Rollback fails — "image not found"	Old image was removed from registry	Re-tag and push the old image, then retry.
Git rollback fails — commit not found	Commit was garbage-collected from the remote	Use a tag instead of a raw SHA.