Read startup failures
EnvironmentFailedError carries error.environment. Its failure identifies the app, code, and message when available. For invalid_settings, fix the named setting instead of retrying unchanged input.
If the environment never ran, State Machines deletes it with reason failed. If an environment previously ran and later fails to start or restart, it becomes failed and keeps its data for one day. A failed environment can be resumed, subject to the underlying failure and its remaining lifetime.
Resolve creation errors
If the dashboard has no matching environments, clear its status and creator filters before deciding which resources need cleanup.
Read your applicable limits with
sm.me(). Do not assume that another workspace or organization has the same allowance.
Recover a timed-out wait
WaitTimeoutError means the SDK reached its wait deadline. It does not prove that startup failed, and it does not delete the environment. The error’s resource is the last successful read, which can be null.
If you retained the environment ID, read it again and either wait for running or delete it. With wait: false, accept creation first, then call wait inside the try block whose finally deletes the environment.
If the create response itself was lost, replay the exact create input with the same idempotency key. Follow operation recovery rather than generating a new key.
UnexpectedStatusError means the requested status requires another action. For example, waiting for a paused environment to become running does not resume it. Call resume() if the task still needs it, or delete it when finished.