client.follow_failed

Following a started run stopped


Type	`https://mthds.ai/errors/client.follow_failed`
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 runtime acknowledged the run, and following it then failed, so the run has started and may still be going or may have ended. The call that started it has taken effect, so it is never repeated automatically.

What to do

Read the run by its id until it ends. Starting it again would run it twice.

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 '`{pipeline_run_id}`' by its id rather than start it again.
Any other reader	`read_run`	Read the run '`{pipeline_run_id}`' by its id rather than start it again.

Detail

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

The client stopped following the run '{pipeline_run_id}', which may still be going.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`pipeline_run_id`	`identifier`	The run.