Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Status codes

How to handle each gRPC status Zingod returns. A rejected SendTransaction is not an error status; it is reported in the response (details).

CodeWhenClient action
UNAVAILABLEthe server is starting, at capacity, or cannot reach its data sources; a stream had nothing to send for 5 minutesretry with backoff
NOT_FOUNDthe height, hash or txid is not in the chain, or is above the index’s tipdo not retry the same request
OUT_OF_RANGEGetBlockRange reached the tip, after sending every block up to itretry once the tip advances
INVALID_ARGUMENTmalformed request, height above the protocol maximum, invalid or wrong-network address, invalid poolTypesfix the request
RESOURCE_EXHAUSTEDrequest body too large (64 KiB; 2 MB + 1 KiB for SendTransaction), or too many address outputs in one requestsend less per request
DEADLINE_EXCEEDEDthe request’s grpc-timeout passed, or the request body took more than 30 seconds to arriveretry with a longer deadline
UNIMPLEMENTEDthe method or shieldedProtocol is unsupported, or its index is disableddo not retry
PERMISSION_DENIEDthe browser origin is blocked by the operatordo not retry
INTERNALserver faultreport to the operator

When the server is at capacity, the UNAVAILABLE response carries grpc-retry-pushback-ms (250). Wait at least that long before retrying.