NO_RELAYER_AVAILABLE
No healthy relayer can be assigned in that shard right now.
| HTTP status | 503 |
| 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
Every eligible relayer is momentarily out of headroom or window budget. This is never answered with a re-sign: the relayer is not lost, only busy.
What to do
Retry shortly. If you already hold a signed transaction, resend the same bytes.
The problem document
Every error is application/problem+json (RFC 9457) with the same shape:
{
"type": "https://docs.co-relayer.com/errors/no-relayer-available",
"title": "No healthy relayer can be assigned in that shard right now.",
"status": 503,
"detail": "A sentence about this specific occurrence.",
"instance": "req_01JB…",
"code": "NO_RELAYER_AVAILABLE",
"retryable": true,
"resign": "SAME_BYTES",
"hint": "Retry shortly. If you already hold a signed transaction, resend the same bytes."
}
See the error model for what each member means and how to handle unknown codes.