Start with identifiers
Persist business request ID, Session/Run IDs, idempotency key, and event cursor. In Console, inspect input, initialization, events, Tools, and resources. Run origin can carry request_id, message_id, and channel for correlation, not authentication or business authorization.Trace a silent task
Query the original Run before submitting again. For authorization/approval waits, inspect the actual invocation. For provisioning, inspect creation operations and stage. For unreachable Runtime, observe recovery of the existing invocation rather than starting another process. If the Run completed, inspect client cursor handling and final result retrieval. SDK entry points includerun, events/stream, tool_calls/toolCalls, and session_initialization/sessionInitialization. Event pages are bounded; drain subsequent pages. Empty data does not prove termination.
Worked investigation: execution failed after cloud restore
A read-only recheck of an existing real failure traced a Modal/OpenClaw OCI Run through its persisted events and the same Session’s resource operations. The sequence wasrun.provisioning → workspace.inputs_verified → run.running → harness.starting → harness.running → harness.exited → run.failed. The terminal diagnostic was harness_execution_failed, exit code 1, Runtime state exited.
The matching cloud create and restore operations were both completed. Two delete operations were completed, and the checkpoint was deleted. This locates the failure after provisioning, at Harness execution; it is not evidence that allocation failed or that resources remain allocated. The diagnostic alone does not identify the Harness’s underlying cause. Preserve that Run and inspect its private execution history before attempting another task. This review created no Run or cloud resource.
To reproduce the investigation with your own failure, query the saved Run, retain its session_id, drain resource-operation pages and select only that Session’s rows. Do not choose the tenant’s most recent operation. Read each relevant operation’s detail/reviews and compare the event stages with its state. Keep actual IDs in your private incident record. The following table covers other possible observations:
Resource details expose
kind, state, provider_resource_id, provider_operation_id, provider_build_id, attempt_count, review_state, last_checked_at, next_check_at, reason and filtered failure. Some are absent when no receipt was obtained. Missing a provider handle is not proof that the request had no effect. Keep actual IDs in a private incident record; public reports should retain the causal sequence without account secrets or task content.
For a shareable health summary, npm run local -- diagnostics /absolute/new-report.json creates a new private-permission file and refuses overwriting. Its allowlisted health projection deliberately omits resource IDs and private endpoints, so it cannot replace your private correlation record. Inspect the report before sharing.