Expand description
Error types for ExecutionClient operations.
§Retry Semantics
Use ClientError::is_transient to determine if an operation should be retried.
Transient errors (connectivity issues, rate limits) may succeed on retry with
appropriate backoff. Non-transient errors (invalid instrument, insufficient
balance) will fail identically on retry — the caller must change the request.
The is_transient() method is the stable contract for retry decisions. Prefer
it over pattern matching on specific variants, as the internal taxonomy may
evolve while is_transient() semantics remain stable.
Enums§
- ApiError
- Represents all API errors generated by an exchange.
- Client
Error - Represents all errors produced by an
ExecutionClient. - Connectivity
Error - Represents all connectivity-centric errors.
- KeyError
- Represents errors related to exchange, asset and instrument identifier key lookups.
- Order
Error - Represents all errors that can be generated when cancelling or opening orders.
Type Aliases§
- Unindexed
ApiError - Type alias for a
ApiErrorthat is keyed onAssetNameExchangeandInstrumentNameExchange(yet to be indexed). - Unindexed
Client Error - Type alias for a
ClientErrorthat is keyed onAssetNameExchangeandInstrumentNameExchange(yet to be indexed). - Unindexed
Order Error - Type alias for a
OrderErrorthat is keyed onAssetNameExchangeandInstrumentNameExchange(yet to be indexed).