CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Seen on:
AWS
Meaning
Rollbacks fail when a resource was changed or deleted outside CloudFormation, a dependency is gone, or permissions changed. Use ContinueUpdateRollback, optionally skipping resources that can’t be rolled back.
Common causes
- Resource modified or deleted manually
- Dependent resource no longer exists
- Service limits or permissions changed mid-rollback
⚡ Quick fix
- Read the UPDATE_FAILED events during rollback
- aws cloudformation continue-update-rollback (with --resources-to-skip if needed)
- Fix drift, then retry the update
Detailed fix by platform
AWS CLI
aws cloudformation continue-update-rollback --stack-name app --resources-to-skip MyBrokenResource
How to diagnose
- Events — Which resource failed to roll back and why
- Drift — detect-stack-drift
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 1104 Cloudflare Error 1104: A variation of this script was not found (Worker route to deleted script)
- already exists in stack CloudFormation: Resource ... already exists (AlreadyExists / already exists in stack)
- Environment health has transitioned to Severe Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most viewed in AWS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026