Skip to main content
CloudFormation could not complete a resource change because something the resource depends on was not there. The failure came from your AWS account’s configuration, permissions, or limits, usually a resource that changed or disappeared outside Fjall’s control.

​
Why this happens

  • A referenced resource does not exist. It was deleted or modified outside Fjall, so the stack has drifted from what CloudFormation expects.
  • A stack export another stack consumes has vanished. The exporting stack was updated or deleted, and the importing resource can no longer resolve the value.

​
How to fix it

  1. Check the dependency chain in the failure detail on the deployment’s detail page. It names the resource that failed and what it was waiting on.
  2. Restore or re-create the missing dependency. If a resource was deleted in the AWS console, bring it back or remove the reference to it.
  3. Run fjall deploy to reconverge the stack. A fresh deploy re-evaluates every dependency and repairs drift where it can.

​
What Fjall shows you

The failure surfaces on the deployment’s detail page on fjall.io, in the CLI’s Error Detail block, and in the deployments list row title. The detail page carries the stable code, a per-occurrence detail sentence, the provider’s verbatim reason, and the remediation steps, along with the dependency chain and root cause resource from the stack analysis.

Deployment safety

How Fjall protects your stacks during a deploy.

fjall deploy

Command reference for deploying an application.

fjall releases

Inspect the state of your deployments from the CLI.