Choose rollback trigger
Define which failures stop live: checkout fail, webhook fail, email fail, data leak, AI cost spike, admin leak.
- Triggers written.
- Owner assigned.
- Pause message ready.
Spare door
Rollback drill
Rollback rehearsal: who decides, what to disable, what to tell users, and how to return to the stable version.
A good launch knows where the exit is while everyone is still smiling.
Find the stable version
Check where to choose previous deployment in Vercel and which env changes cannot be rolled back automatically.
- Previous deployment identified.
- Env diff reviewed.
- DNS/domain impact understood.
Communicate safely
Prepare customer and support messaging if access is temporarily unavailable.
- No blame language.
- Support channel included.
- ETA not invented.
checklist
What to check
- Rollback trigger list exists.
- Previous deployment known.
- Env diff known.
- Pause copy ready.
- Support escalation ready.
red flags
When to stop
- Only one person knows rollback.
- Rollback requires editing secrets in panic.
- Customers see stack traces or internal status.
done when
Definition of done
- Rollback can be described in five written steps.
- A pause message exists.
- Support knows who decides go/no-go.
related doors