VFX-E-1601¶
Title¶
NoRunToExplain
Explanation¶
No eventsPath was given and no run has finished in the run registry. explain_run/diagnose_run
default to the most recent finished run recorded in the registry when eventsPath is omitted; this
code fires when there is no such run to default to. When the server is launched with --workspace,
the registry persists across server restarts — so this code can fire even if past runs completed in
prior sessions.
Common causes¶
explain_run/diagnose_runcalled with noeventsPathbefore anyrun_suitecall has completed and been recorded in the run registry.- The server was started without
--workspace, so the registry is session-scoped and a new process lost the in-memory record (exactly like the prior session-only behaviour). - Intentionally trying to explain a run from a different registry instance (e.g. a different workspace), without passing its events path explicitly.
Fixes¶
- Run
run_suitefirst, then callexplain_run/diagnose_runwith noeventsPathto use the most recent finished run automatically. - Pass
eventsPathexplicitly, pointing at a specific run's events file, to explain a run regardless of server mode or registry state. - When the server is not launched with
--workspace, the registry is session-scoped; restart the server or start it with--workspace <path>to persist runs across restarts.