The transition is named by the endpoint rather than sent as a value, so this boundary can
only ever ask for this one change — there is no way to ask the server for an arbitrary
status. It is a mutation, so it acquires a CSRF token. The response confirms the committed
change; the authoritative current state is still the queue read, which the caller refreshes.
A 409 CONFLICT means the order was no longer queued — the operator tapped twice, or
another screen had already acted. That is an expected outcome of a fast control rather than
an error to retry blindly, and it reaches the caller as a rejected promise.
Advance one queued order to
Preparing.The transition is named by the endpoint rather than sent as a value, so this boundary can only ever ask for this one change — there is no way to ask the server for an arbitrary status. It is a mutation, so it acquires a CSRF token. The response confirms the committed change; the authoritative current state is still the queue read, which the caller refreshes.
A
409 CONFLICTmeans the order was no longer queued — the operator tapped twice, or another screen had already acted. That is an expected outcome of a fast control rather than an error to retry blindly, and it reaches the caller as a rejected promise.