|
Status |
Description |
|
Launching / Initiating |
Cloud infrastructure is being created - i.e - EC2 instances, VPC, load balancers etc. |
|
Launching / Deploying |
Application scripts are running - deployment is in progress. |
|
Active |
Health check runs in parallel to the start scrip and once all applications have passes it successfully, the sandbox deployment is complete and the sandbox is active. |
In case of errors, the sandbox may reach the following statuses:
|
Status |
Description |
|
Active with error / Manually aborted |
The user asked to abort the sandbox after it started launching |
|
Active with error / Launch Failed |
Something went wrong that prevented the sandbox from moving to 'Active' status |
That includes all types of errors:
- Errors returned from the cloud provider (for example: reaching AWS infrastructure or budget limits).
- Deployment errors, such as a script failing to execute
- Health check failures, meaning not being able to identify a successful deployment after a certain amount of time.
It is important to understand that the status Active with error indicates that the sandbox is indeed active and is ready for debugging and troubleshooting.
For information about troubleshooting the sandbox deployment see, Troubleshooting Sandbox Launch.