2.4 compatibility in Nexa 3.0
This page describes the retained 2.4 language/runtime path. Sources without a version declaration use this path. Start new Open Programs with Nexa 3.0; compare contracts in the migration guide.
Diagnostics and stop-state index¶
Locate failures using actual exceptions, Harness rule IDs, and RunState.status. The previous page's E001–EC02 labels were explanatory categories; the current CLI output is authoritative.
| Identifier | Layer | Guidance |
|---|---|---|
CompilationError |
Parsing, includes, generated syntax | Unified compilation |
| Harness rule ID | Static budgets, tools, context constraints | Harness |
waiting_approval |
Paused execution | Approval |
failed |
Provider, tool, or output validation | Troubleshooting |
cancelled |
Cooperative cancellation | Execution |
timed_out |
Total deadline | Budgets |
budget_exhausted |
Model/tool/token limit | Budgets |
CheckpointConflict |
Revision conflict | Checkpoints |
ToolOutcomeUnknown |
Uncertain side effect | Unknown outcomes |
pass/fail/skip/error |
.nxintent evidence status |
Verification |
Preserve source path, line/column, original message, and run ID when presenting diagnostics. Results without source spans should show parsing errors without guessed navigation targets.
Source and validation · compilation / execution / verification