pipelex.storage.not_found

A stored file is gone


Type	`https://docs.pipelex.com/errors/pipelex.storage.not_found`
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	`no`: repeating the operation fails the same way
HTTP status	`500`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

A file the run wrote, or that the runtime handed out, is no longer in storage. A caller's own reference to something that does not exist is input.reference_not_found instead.

What to do

Report the problem to whoever runs the runtime, with the run's pipeline_run_id when it has one.

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	`report`	Report this to whoever runs the runtime.
Any other reader	`report`	Report this to whoever runs the runtime.

Detail

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

A file the runtime stored is no longer in its {scheme} storage.

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 no longer holds the file: one Pipelex ships, or `plugin` for a storage plugin's own.