SDKs
Errors and retries
Failures surface as EbbmemError. The code field is the EBB- value from the error envelope.
EbbmemError carries status, code, message, details, and request id (the X-Request-ID header). The code is the EBB-… field of the error envelope. The schema example is EBB-100-AUTH-001. The schema default is EBB-500-INTERNAL.
- AuthError: 401 and 403.
- NotFoundError: 404.
- ValidationError: 400 and 422.
- RateLimitError: 429, with retry_after when the response provides it.
- ServerError: 5xx.
- ConnectionError: no response.
Python uses snake_case fields (request_id, retry_after). TypeScript, Java, and C# use requestId and retryAfter. Go returns *ebbmem.Error with exported fields, wrapped by *AuthError and the other pointer types. errors.As matches both the wrapper and *ebbmem.Error.
Rust leaves request_id empty. Its generated response error has a status and a body and no headers, so a 429 is retried with exponential backoff and Retry-After is not read.
Backoff is min(8, 0.2 * 2^attempt) seconds plus jitter. A numeric Retry-After replaces that delay on 429, except in Rust.
Retry connection errors, 429, and 502, 503, and 504. Retry only idempotent methods: recall, recallFederated, get, list, status, whyNot, health, ready, tasks get, list, and cancel, and forget. Also retry remember and rememberBatch when the caller set an idempotency key. The header name is Idempotency-Key.