Observability

Track command responses, authentication expiry, subscription acceptance, heartbeat age and data freshness separately. A reachable service does not establish that a private account channel is authorized, and a readable history response can still lag current execution.

When diagnosing a problem, record the environment, affected market, safe request identifiers and the relevant sequence domain. Redact authorization headers, realtime tickets, connect codes and signing material from logs. Avoid including sensitive account data in shared diagnostic reports.

Check both transport health and the data your application needs. A public market stream can remain active while a private account subscription has expired or been dropped.

Connection. Monitor heartbeat age, authentication and accepted subscriptions.

Data. Check identity, continuity and completeness before marking a view current.

Actions. Continue only when the required market and account state is available. Preserve unresolved command identities while recovery establishes their outcome.

Query services build snapshots and history from committed execution and confirmed settlement evidence. Their timestamps and completeness describe the view returned by that operation. A recent update in one account view does not establish freshness for every other view.

Use supported WebSocket payloads for ongoing changes. If a required field or replay range is unavailable, keep the affected value visibly stale or incomplete. Do not synthesize missing history or treat an order acknowledgement as a fill or settlement confirmation.

Committed execution feeds live delivery and historical queries. Canton confirmation adds settlement facts later. These views serve different purposes and may update at different times.

Live delivery. Market and account streams publish supported updates for accepted subscriptions.

History. Query views support account inspection and history, with operation-specific freshness and completeness.

Closed-position recovery. Positions that close while realtime delivery is unavailable may be absent from closed-position episode replay after restart. Treat that history as incomplete until a supported recovery path establishes the missing records; reconnecting alone does not reconstruct them.

Define how your application behaves when a subscription is refused, private access expires, market data becomes stale or a command result is unknown. Keep already-submitted orders distinguishable from new commands, and pause automated actions when their required state is unavailable.

Edel Markets is on Devnet, with Testnet and Mainnet coming soon. Check the target environment’s markets, permissions and supported channels before use. A connection becoming healthy again is the start of recovery; it does not by itself confirm that account data or history is complete.