Appearance
Troubleshooting
| Symptom | Check and next action |
|---|---|
Missing PlanStepTree or language interface | Verify the exact language snapshot in Installation; public 1.0.8 is incompatible. |
| Driver not found | Activate the correct environment and install the simulator wheel. --driver selects a plugin; it does not download one. |
| GitHub release returns 404 or access denied | Check the release tag and asset URL against the installation page. Public release downloads do not require GitHub CLI authentication. |
| Binding or workspace mismatch | Use the program and configuration from the same snapshot. Check allocation IDs and compiled-plan selection. |
| Resident socket not found | Start serve first, check its log and socket path, then use host-status. |
| Another owner or resource conflict | Check whether a host or unresolved run already owns the station. Do not create a competing owner. |
| Tips remain used after changing output directory | Station consumption is persistent. Use a new station ID only for an independent simulation. |
| Body succeeded but run is finalizing | Inspect cleanup and resource-release evidence; body success is not terminal completion. |
needs_reconciliation or unknown outcome | Keep the run and station records. Do not clear state or blindly retry the affected action. General manual reconciliation is not implemented. |
| Unsupported operation or parameter | Check the supported profiles; language validity does not imply instrument support. |
Capture a Useful Report
Keep the command, source/configuration snapshot, exit status, terminal messages and run ID. Include the relevant result.json, diagnostics and recorded device evidence. Resident reports should also include host-status, status and device-status output.
Run databases and configuration may contain experimental or operational information. Review them before sharing. Preserve originals locally for investigation.
Recovery Boundaries
A stopped process does not prove that its last device action failed. Recovery uses durable evidence and matching saved configuration. The current system does not provide a general user command to adjudicate every unknown physical outcome, automatically reconnect instruments or undo completed actions.