client.outcome_unknown

The call may have created a run


Type	`https://mthds.ai/errors/client.outcome_unknown`
Family	`client`: What a client detects itself, and never receives as a response body.
Domain	`runtime`: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem
Retry	`outcome_unknown`: the operation may already have taken effect, so its outcome is learned before anything is repeated
HTTP status	none (client)
Raised as	an error a client detects itself, never received from a runner

What it means

The connection dropped, the call timed out, or the caller stopped it, after a request that creates a run had left, so the run may exist.

What to do

Read the run by its id when the client knows it. A client that knows no run to read leaves the outcome unknown and never repeats the request automatically, since a repeat may start a second run.

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	`read_run`	Read the run if its id is known, and otherwise leave the outcome unknown rather than send the request again automatically.
Any other reader	`read_run`	Read the run if its id is known, and otherwise leave the outcome unknown rather than send the request again automatically.

Detail

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

The connection was lost after a request that creates a run had left, so the run may exist.

Parameters

A parameter is present on every occurrence of the code unless it is marked optional, and one marked operator-only reaches only whoever runs the runtime, never a caller.

Name	Type	Description
`pipeline_run_id`	`identifier` (optional)	The run, when the client learned its id before the connection was lost.