Skip to main content
Fjall classifies every failed deployment into a stable dotted code, such as cfn.permissions or ecs.circuit_breaker. Find your code in the tables below, then open its page for the cause and the fix.

​
Where the code appears

  • On the deployment’s detail page on fjall.io
  • In the CLI’s Error Detail block after a failed fjall deploy
  • In the deployments list row title
Each code pairs with a stable title, a per-occurrence detail sentence, the provider’s verbatim reason, and remediation steps. Every code also states fault attribution: whether the failure came from your AWS account’s configuration, from your application’s code, from Fjall’s platform, or could not be attributed automatically.

​
CloudFormation failures

​
ECS failures

​
Unclassified failures

The suffix names the phase the failure was located in. Nine suffixes ship today, and all of them resolve to the same page: unclassified.preflight, unclassified.credentials, unclassified.synth, unclassified.bootstrap, unclassified.image_build, unclassified.image_push, unclassified.cloudformation, unclassified.ecs_stabilise, unclassified.platform Read the suffix as a narrowing hint. unclassified.image_build points at your Dockerfile and build inputs, unclassified.cloudformation points at the stack update.

​
The taxonomy grows

New codes are added as recurring failure shapes earn them. The classification schema is versioned, so stored failures can be reclassified when a shape they match gains its own code.

​
Next steps

Deployment safety

The boot gate, ECS circuit breaker, and watchdog that catch a bad deploy.

fjall deploy

Deploy an application and read the CLI’s failure output.

Deploy an application

The full deployment pipeline, phase by phase.

Destructive changes

Consent gates that stop a deploy before it replaces or deletes AWS resources.