Single error struct returned from DustEcto.Repo when transport
failures or server errors occur. Validation errors return
{:error, %Ecto.Changeset{}} instead — that path is unchanged.
Kinds
:network— Req call failed before reaching the server (connection refused, DNS, TLS, etc.).retryable?istrue.:http— server replied with a non-2xx, non-recognized status.detailcarries the status + body. Usually retryable on 5xx, not on 4xx.:conflict—If-Matchprecondition failed.detailcarriescurrent_revisionand (for batch_write)op_index+path.:not_supported— feature unavailable on the active transport (e.g.subscribein HTTP mode). Not retryable.:nothing_to_write—Repo.insert/updatehad no fields to send. Not retryable; usually a bug in the caller's changeset.:timeout— sync write didn't get an ack within the configured window. The write may still eventually succeed; do not retry blindly.:unauthorized— token rejected by the server.:invalid_params— server rejected the request shape.:rate_limited— server returned 429.detailmay includeRetry-After.:not_implemented— server returned a whole-route 404 (the method/path isn't registered). Usually means the deployed Dust server is older than the SDK expects. Distinct from:not_found, which is an entity miss inside a working route.
Summary
Functions
Construct an error of the given kind.