Debugging

Good to Know

We have tried out best to build the UI and UX of the application creation and modification in a manner that limits deployment failures. However, there are always edge cases that do occur from time to time. If you like to report these issues please don't hesitate to reach out on Twitter or Email

How to Debug

To understand the reason why the deployment is failing, follow the following steps:

• Go to AWS Cloudformation Service in the region selected for the app

• Click the Stack with the failure

• Scroll through the Events tab and failure reason will be listed beside the resource that failed to deploy

The reason listed will give you an understanding on why deployment for the stack is failing.

Failure Statuses

Listed below are possible failure statuses that you may see:

• CREATE_FAILURE - Application failed to get created, hence the application hasn't been deployed.

• REVIEW_IN_PROGRESS - Similar to CREATE_FAILURE, the application stack set was created but there are issues with the data entered, hence no deployment has taken place.

• ROLLBACK_COMPLETE - There was an issue with the deployment of stack. It was reverted back to a previous state.

• UPDATE_FAILED - Deploying the update of the stack failed. Changes you made in the application haven't been deployed.

• UPDATE_ROLLBACK_COMPLETE - Deploying the update of the stack failed and it has been reverted to previous state.
  
  AWS's Explanation on Failures