Monitoring
Read status, timestamps, decisions, orders, and stored results together.
Monitor a session as a chain of evidence: data arrived, the strategy evaluated it, a request was made or skipped, execution produced an outcome, and the visible state reflects that outcome.
Check the right surface
| Surface | What it helps establish |
|---|---|
| Status and server identity | Which run you are viewing and its reported lifecycle state |
| Chart and input timestamps | Whether the expected instrument and observations are arriving |
| Logs | Initialization, strategy decisions, errors, and request diagnostics |
| Orders | Pending or rejected requests and their identities |
| Positions and trades | Current exposure and recorded execution outcomes |
| Script/model state | Cached evidence and the decision's recorded inputs |
A RUNNING label does not establish fresh data. A plotted signal does not establish an accepted order. A trade total does not explain why an individual action occurred.
Investigate one event
Find the first unexpected bar, then align market time, decision logs, request metadata, and execution records. The time when the UI displayed an update can differ from the market timestamp used by the strategy.
Check whether the state belongs to the current run, instrument, or active market. Cached diagnostics can remain after an event expires; use freshness and identity fields rather than treating all displayed state as current permission to trade.
Live versus stored views
When the remote session is available, the console can display live state. When it is not, stored server data supports later inspection. Stored snapshots are not a live broker-account query and may not contain every in-memory update from before disconnection.
For a multi-app server, select the intended leader or follower before reading its trades and logs. Related runs are grouped by the leader server identity, not only the saved app ID.
Reconnect and stream behavior
The optional stream view uses incremental updates. Slow or disconnected clients can miss recent deltas; refresh to obtain a new snapshot when displayed state appears inconsistent.
A browser disconnect does not itself prove the backend stopped. Confirm server status and account outcomes separately before deciding whether to restart or launch another instance.
Continue with troubleshooting.