Errors
dblurt exposes typed error metadata so applications can respond to error categories and retryability without parsing human-readable messages.
Error model
The important application-facing metadata is:
| Field | Meaning |
|---|---|
category | Broad error family such as validation, transport, timeout or RPC application error. |
code | Stable SDK code such as DBLURT_TIMEOUT. |
retryable | Whether the error category appears transient. This is not permission to blindly repeat side-effectful operations. |
field / path | Optional SDK validation location. |
rpc_code / rpc_data | Optional JSON-RPC application error details. |
Exact API shape: DBlurtErrorMetadata.
Main APIs
Retry guidance
retryable: true means the failure appears transient. It does not mean every operation is safe to retry.
| Workflow | Retry posture |
|---|---|
| Read-only call | bounded retry/backoff is usually reasonable. |
| Local operation builder | retry is usually irrelevant; fix the input. |
| Broadcast with ambiguous network result | inspect chain state before resubmitting. |
See Handle retryable errors for a task-oriented example.