Skip to content

method.changed_concurrently

A method file changed while it was being fixed

Type https://mthds.ai/errors/method.changed_concurrently
Family method: The method as written, the validation vocabulary included.
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 409
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 a fix read was changed by someone else before the fix wrote it, so the fix stopped rather than overwrite the change.

What to do

Reload the method's files, and apply the fix to their current content.

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 refresh Read the method's files again, then apply the fix to their current content.
Any other reader refresh Read the method's files again, then apply the fix to their current content.

Detail

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

A file of the method changed after the fix read it and before the fix wrote it.

Parameters

This code declares no parameters, so its problems carry no params.

See also