Deployments
Roll back
Something went wrong in production? Roll back to a prior deployment in seconds — no rebuild, no re-push.
How rollback works
DunOps lists your recent deployments for the target project, identifies the previous stable one, and swaps the production alias back to it. Like promotion in reverse — the built artifact is already deployed; DunOps just changes which one is live.
1
Tell DunOps to roll back
Describe which project and optionally which specific deployment to revert to — plain English, no deployment IDs required.
2
Review the plan
DunOps shows the current deployment SHA and the target to revert to so you can confirm before anything changes.
3
Approve
The rollback runs — production traffic shifts immediately to the prior deployment.
Example prompts
chat
Roll back the last production deploy on my storefront
Revert my Netlify site to the previous deployment
Roll back Vercel to the deploy before today's releaseDatabase migrations are not rolled back
Data caveat
Rolling back a deployment does not undo database migrations. If your rollback target is incompatible with the current schema, your app may error. Review your migration state before approving a rollback in production.