Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
Seen on:
AWS
Meaning
When a new stack fails to create, CloudFormation deletes what it made and leaves the empty stack in ROLLBACK_COMPLETE. You must delete it and create again — after fixing the original failure, which is in the stack events.
Common causes
- Initial stack creation failed (permissions, name conflicts, invalid properties)
- Re-running deploy against the failed stack
⚡ Quick fix
- Find the first CREATE_FAILED event for the real reason
- Delete the stack, fix, deploy again
- SAM/CDK: deploy will work after deletion
Detailed fix by platform
AWS CLI
- bash
aws cloudformation describe-stack-events --stack-name app --query "StackEvents[?ResourceStatus=='CREATE_FAILED'].[LogicalResourceId,ResourceStatusReason]" --output table aws cloudformation delete-stack --stack-name app
How to diagnose
- Events — First CREATE_FAILED reason
- Status — describe-stacks
🔧 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