Skip to main content
Let the Runner, active reader, and manual editor stop before inspecting a quiescent Record. Sample selection and ReportInput construction for an export must also have finished; later Report execution and site writing do not access the Record. Then query an explicit Run instead of guessing from a directory name or time.

The Record cannot be found or opened

Do not replace these errors with an empty result. Repair the named path or file, then read again.

An expected result is missing from the Sample

A Sample preserves the expected-slot denominator for its Run. Check each slot’s state on the page: To see what the next run will do, first run:
The output identifies whether each slot executes, is carried, or waits for an explicit accepted Member. It also explains why adoption conditions are not met.

A channel is unavailable or fails

A channel state affects only the page or Calculation that requested it: unavailable does not mean unsupported, and unsupported does not mean invalid. A requested invalid channel fails that request. An unrequested channel does not block an unrelated page or export.

An edit is not visible

show and view create one fixed ReportInput for a command. If you edit a Verdict, Usage, or another channel after the Record becomes quiescent, end the current viewer and run it again:
Do not run a Runner or active reader while editing. An export holds its reader only while it selects the Sample and creates ReportInput; Report execution and site writing no longer access the Record afterward.

JSON has no receipt

npx niceeval exp <experiment> --json writes its final receipt only after it successfully creates an Invocation. If input validation fails first, there are no runIds to inspect. Correct the Experiment, Eval selection, or command argument and run it again. When it succeeds, use the receipt’s runIds with show, view, or view --out.

A static report site cannot export

view --out can export only planned pages, downloads, and assets. A requested invalid channel, missing asset, network URL, bad path, or symbolic link makes the export fail. Correct the error and export again. A successful static directory includes a StaticAssetManifest and opens in an offline browser; it does not read the source Record. See Viewing Results and Publish a Static Report for the full workflows.