Tasks, receipts and incident investigation

Use Monitor in the selected application for durable execution. Tasks opens the assigned work view. Record the exact scope, task or job ID, original request key and time window before a recovery action.

1. Open the task by ID in Durable application tasks. Compare its function, state and Timeline. Choose Read logs under Worker diagnostics. Follow child job IDs when a workflow has multiple effects. The task timeline can be available even when the worker has no source diagnostic text.
2. For a published typed job, use its Job ID under Your typed jobs and choose Inspect publication receipt. Compare the committed revision and scope with the original request. For a completed export, follow its request ID to the exact artifact.
3. Use Governed controls only when the task advertises the relevant action. In the disposable export example, Request interruption records Interrupted on the original task. Create distinct rerun uses a new key and creates a new task ID. Replaying that same rerun intent with its same key returns the same new task ID. Browser interruption and rerun procedure

For a lost response, use the original request identity and the applicable exact-replay contract. A missing receipt leaves the outcome uncertain. Check already committed effects before considering an interruption or rerun, and capture only bounded diagnostics in incident records.