pipelex.sandbox.unavailable

The Daytona sandbox could not be started


Type	`https://docs.pipelex.com/errors/pipelex.sandbox.unavailable`
Family	`pipelex.sandbox`: The Daytona sandbox that runs a method's own code.
Domain	`runtime`: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem
Retry	`yes`: repeating the operation may succeed, after `retry_after` seconds when the problem gives it
HTTP status	`503`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

A Daytona sandbox, or the local subprocess that stands in for it, could not be provisioned or reached. The method's own code never ran, so running the method again is safe.

What to do

Run the method again after a while. If the Daytona sandbox keeps failing, report it to whoever runs the runtime.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, whoever made the call, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`retry`	Run the method again after a while.
Any other reader	`retry`	Run the method again after a while.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

The Daytona sandbox that runs the method's code could not be started (backend: {backend}), so the code never ran.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`backend`	one of `daytona`, `subprocess`	What could not be started: a Daytona sandbox, or the local subprocess that stands in for it.