Trading Contour
Runtime States
How the cabinet receives and displays trading contour state.
English localization is preserved as a draft. It uses the same claim IDs and status model as the Russian source, but remains noindex until editorial review.
The cabinet does not show state from a button alone. It combines run status, fresh runtime request, heartbeat and exchange/order evidence. Transitional states can therefore differ from the last confirmed heartbeat.
This public reference still needs Trading/Frontend review because UI labels, backend statuses and engine mode names are not fully aligned.
Verified Sources
- `runtime_control_requests` for pending, claimed, applied and failed requests.
- `user_runtime_heartbeats` for active, paused, stopping, stopped and failed.
- Order reports as an additional active-order signal.
- Freshness windows: 180 seconds for open request and 120 seconds for applied request.
User-Facing States
| State | Meaning |
|---|---|
| Starting | A fresh start request or preparation evidence exists. |
| Active | Fresh heartbeat or active exchange evidence exists. |
| Pausing | A fresh pause request exists. |
| Paused | Heartbeat or applied request confirmed pause. |
| Stopping | A fresh stop request exists. |
| Stopped | Run or heartbeat confirmed stopped. |
| Stale | Heartbeat is stale or run status needs new evidence. |
| Failed | Worker or heartbeat reported failure. |
Limits
This page is not indexed as final until canonical state vocabulary is approved across UI, backend and engine.