On occasion you may see that a blueprint or node as gone from stable to 'on fire' as shown below.
Clicking on the application will show the following:
Further details of the cause can be gained by going into the 'Activity' Tab and click through on the process that failed:
The key part is the
code='', message='' circled in red. From this we can see that the error was caused by the AWS deployment target being unavailable:
To verify we can also click further in and see exactly where in the deployment cycle it failed. This confirms that it did indeed fail on the AWS provisioning:
Scrolling down can show a much more detailed status about the error including the exact processes that failed and how long each one had taken: