Rollbacks let you quickly revert to a previous version when something goes wrong. TurtleApps keeps a history of all deployments, making rollbacks safe and instant.

When to Rollback

Critical bugs discovered in production
Performance degradation
Security vulnerabilities
Failed third-party integrations
Any unexpected behavior affecting users

✨Don't Hesitate

If something looks wrong after deployment, rollback first, investigate later. A quick rollback minimizes user impact.

How to Rollback

Go to Deployments

Navigate to your project's Deployments page to see deployment history.

Deployment history list

[Screenshot placeholder]

Select Previous Version

Find the last known good deployment. Each deployment shows:

Timestamp
Associated ticket
Who deployed it
Status

Click Rollback

Click the "Rollback" button on the target deployment.

Confirm

Review the rollback details and confirm. The rollback begins immediately and typically completes in under a minute.

What Happens During Rollback

Previous deployment artifacts are retrieved
Current deployment is replaced
CDN cache is invalidated
Health checks verify the rollback

⚠️Data Considerations

Rollbacks restore code only, not database changes. If your deployment included database migrations, you may need to handle those separately.

Rollback History

TurtleApps retains deployment history based on your plan:

Plan	History Retention
Starter	7 days
Professional	30 days
Business	90 days
Enterprise	Custom (up to 1 year)

Automatic Rollbacks

Enable automatic rollbacks in Project Settings → Deployments. When enabled, TurtleApps automatically rolls back if:

Health checks fail after deployment
Error rate spikes above threshold
Response time exceeds limit

Best Practices

Test thoroughly in preview before deploying
Keep deployments small for easier rollbacks
Monitor metrics after deployment
Document what changed in each deployment
Have a communication plan for incident response