Troubleshooting

Start with the error shown in the workspace and the status of the selected run or task. Keep the relevant revision and run identifiers when describing a problem.

My edits disappeared after a refresh

Editor changes need Save revision, Run backtest, or Send to become a saved checkpoint. There is no background durable draft autosave. Check History for the latest saved source.

A newer revision blocks saving

Another writer, including the assistant, advanced the experiment while your draft was based on an older revision. Preserve the local text you need, load the latest revision, and reapply the changes. See revisions.

The run failed or produced no trades

Check the run error first. Unsupported data modes, missing history, source errors, and output limits require different fixes. For a completed run with no trades, inspect warmup, signal conditions, order guards, and fill delay in order. Follow the engine's debugging guide.

Imported strategies can retain a native SJS module path, which takes precedence over inline SJS source. If inline edits have no effect, inspect the imported app's source configuration; use a fresh inline-SJS experiment when you intend to test the editor's source.

The assistant stopped

Inspect the task status, usage, and error. A token budget, timeout, cancellation, provider error, or missing provider usage report can stop a task. Saved revisions and completed results can still be useful; inspect them before sending a follow-up.

If the model connection fails, verify the selected connection and model. Backend Codex depends on the backend host's configured login and model catalog.

Live updates disconnected

The UI falls back to reading saved state while reconnecting. Preserve unsaved editor changes before refreshing. A connection interruption does not itself cancel a running backend task.

A backend restart is different: queued work is not recovered and active work is not automatically resumed. Activity can remain visible briefly until its lease expires. Once the task is shown as interrupted or inactive, inspect saved checkpoints and retry the intended work.

Publishing reports a conflict

The imported app changed after import. Create a separate app or import the latest app into a new experiment before updating it. Repeatedly retrying the stale snapshot will not resolve the conflict.

The workspace is cramped

Use Agent, History, and Settings to hide panels you do not need. The side panels can be resized. On narrow screens, the workspace can scroll horizontally.