ROLLBACK_COMPLETE AWS Origin: Platform & cloud Last updated 13 Oct 2026

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.

Exact message you may see is in ROLLBACK_COMPLETE state and can not be 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

  1. Find the first CREATE_FAILED event for the real reason
  2. Delete the stack, fix, deploy again
  3. SAM/CDK: deploy will work after deletion

Detailed fix by platform

AWS CLI

  1. 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

  1. Events — First CREATE_FAILED reason
  2. 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:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1104 — Cloudflare Error 1104: A variation of this script was not found (Worker route to deleted script) (Cloudflare)1104already exists in stack — CloudFormation: Resource ... already exists (AlreadyExists / already exists in stack) (AWS)already exists in sta…Environment health has transitioned to Severe — Elastic Beanstalk: Environment health has transitioned from Ok to Severe (AWS)Environment health ha…field is immutable — The Deployment is invalid: spec.selector: Invalid value: field is immutable (Kubernetes)field is immutableInvalidTemplateDeployment — ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate (Azure)InvalidTemplateDeploy…Multi-Attach error — Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another (Kubernetes)Multi-Attach errorNo job functions found — Azure Functions: No job functions found. Try making your job classes and methods public / Error indexing method (Azure)No job functions foundNo updates are to be performed — CloudFormation: No updates are to be performed (AWS)No updates are to be …ROLLBACK_…

Explore the map of this error Full error map →

🧠 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.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.