session-recovery

To resume a long-running task after an interruption, you maintain an execution log recording current status, active phase, and last completed task. This allows you to accurately resume work from the exact point of pause.

The best way to maintain session progress for multi-phase workflows is by creating an initial execution log at the start and appending progress after each task. This records status and planned next steps for quick resumption.

An execution log helps with session recovery by recording current status, active phase, and last completed tasks. It enables quick resumption with context, notes, and planned next steps after a pause or failure.

You need to track session progress for interrupted tasks when working with multi-phase workflows that may experience pauses or failures across iterations. Recording status ensures work can resume accurately without losing context.

Yes, you can use session recovery for workflows that fail across iterations. It supports multi-phase workflows by maintaining an execution log to record status and last completed tasks, ensuring accurate resumption after potential failures.

Using an execution log for task recovery requires manually creating the initial log at the start of your plan and consistently appending progress after each task to ensure accurate resumption. It does not automate this logging process.