NONCE_IN_FLIGHT
Another intent already holds this nonce.
| HTTP status | 409 |
| Group | Relay path |
| Retryable | Yes — the same request may be sent again |
| Re-sign | SAME_BYTES — resend the transaction you already have, byte for byte |
What happened
One nonce carries one transaction at a time; a second signature for it would be a second send.
What to do
If resign is SAME_BYTES, resend the identical bytes — that is safe. Otherwise wait for the in-flight intent to settle, or cancel it.
Extra members
This code carries occupiedBy, pinnedNonce in the problem document, on top of the common members.
The problem document
Every error is application/problem+json (RFC 9457) with the same shape:
{
"type": "https://docs.co-relayer.com/errors/nonce-in-flight",
"title": "Another intent already holds this nonce.",
"status": 409,
"detail": "A sentence about this specific occurrence.",
"instance": "req_01JB…",
"code": "NONCE_IN_FLIGHT",
"retryable": true,
"resign": "SAME_BYTES",
"hint": "If `resign` is `SAME_BYTES`, resend the identical bytes — that is safe. Otherwise wait for the in-flight intent to settle, or cancel it."
}
See the error model for what each member means and how to handle unknown codes.