RESIGN_REQUIRED
The assigned relayer can no longer be used, so the transaction must be signed once more.
| HTTP status | 409 |
| Group | Relay path |
| Retryable | No — sending it again changes nothing |
| Re-sign | NEW_SIGNATURE_SAME_NONCE — one new signature, same nonce, new relayer |
What happened
The relayer is no longer renewable, or its exposure headroom or hourly signing budget is spent on every host that holds its key. Nothing was signed or broadcast.
What to do
Take the new relayer from the assignment member, rebuild the transaction with the same nonce, and have the user sign it — once.
Extra members
This code carries assignment 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/resign-required",
"title": "The assigned relayer can no longer be used, so the transaction must be signed once more.",
"status": 409,
"detail": "A sentence about this specific occurrence.",
"instance": "req_01JB…",
"code": "RESIGN_REQUIRED",
"retryable": false,
"resign": "NEW_SIGNATURE_SAME_NONCE",
"hint": "Take the new relayer from the `assignment` member, rebuild the transaction with the same nonce, and have the user sign it — once."
}
See the error model for what each member means and how to handle unknown codes.