Troubleshooting
Locate app, launch, data, execution, and history problems without guessing from one status label.
Keep the saved app identity, server identity, selected broker/environment, and first unexpected timestamp with your report. In a group, include the selected follower as well as its leader.
App or publication problems
If changes are missing, verify that the editor saved successfully and that the server uses the intended app or runtime copy. In Agent Lab, check the publication revision independently from the selected run.
An imported-app update conflict means the saved app changed since import. Use a fresh import or create a separate candidate rather than assuming the old experiment remains synchronized.
Launch problems
| Symptom | Checks |
|---|---|
| App cannot be selected or found | Workspace access, saved app identity, and current configuration |
| Broker required or unavailable | App family, intended account, connection availability, and launch compatibility |
| Multi-app validation fails | Supported leader target, at least one follower, compatible types, and unique instruments |
| Server path already used | Existing run with that path; inspect it before trying another launch |
| Capacity or startup error | Exact launch error, workspace availability, and whether a server record was created |
A session runs but appears inactive
Check incoming timestamps and logs before changing the strategy. Missing data, insufficient warmup, session filters, a false condition, or an observation-only source can all produce no trades legitimately.
Check automation mode and L3 decisions next, then pending orders and broker responses. A RUNNING label does not establish that a request was made or accepted.
Behavior differs from the historical test
Compare the exact source, instrument, initialization data, interval, timezone, account state, and execution adapter. Live open-bar updates and synthetic fills can differ materially from historical replay.
Use market-data debugging, order debugging, and the relevant source guide to isolate the first changed event.
The UI disconnects or shows old results
Determine whether the view is live or stored. Refresh a stale incremental stream and confirm server status independently. Do not launch a duplicate simply because one browser stopped receiving updates.
Stored server results are useful evidence but are not a fresh broker-account query. Check positions and outstanding orders separately, especially after stopping or terminating the runtime.