Errors / conflict
conflict
The machine, or the call, is not in a state where this can happen yet.
When it happens#
- The machine cannot do it in its state, such as pausing a machine that is not running.
- The machine's files cannot be reached just now, because it is not on a server (stopped or archived, for example): start it first.
- The first call with the same
Idempotency-Keyis still running.
What to do#
Look at the machine's state (wm machines get <machine>), bring it where it needs to be (start it), then try again. For an Idempotency-Key still in use, wait a second and send the same call again.
Send it again? Yes, once the state is right; after Retry-After for an Idempotency-Key still in use.
Every code, and how to read a refusal: Errors.