pipelex.storage.unavailable

Storage is unavailable


Type	`https://docs.pipelex.com/errors/pipelex.storage.unavailable`
Family	`pipelex.storage`: Pipelex's storage addresses and uploads.
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

The storage backend failed a read or a write, which may succeed later.

What to do

Send the request again after retry_after seconds when the problem gives it. If storage 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`	Send the request again after a while.
Any other reader	`wait`	Wait, then send the request again.

Detail

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

The {scheme} storage failed a read or a write.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`scheme`	one of `local`, `s3`, `gcs`, `memory`, `plugin`	The kind of storage that failed: one Pipelex ships, or `plugin` for a storage plugin's own.