A Claude-based system processes financial reports in nightly batches. During a server restart at 3 AM, processing stops with only partial completion. On restart, the system must resume without reprocessing completed reports or skipping incomplete ones. Which pattern enables correct recovery?

Question

Accepted Answer

B. Maintain a manifest file that lists all tasks with their completion status, updated atomically as each task completes, and read on restart to determine what needs to be processed or retried. The manifest file pattern is the CCA-F-recommended approach for crash recovery: write a manifest before starting that lists all tasks; update completion status as each task finishes; on restart, read the manifest to skip completed tasks and retry incomplete ones. This ensures no work is duplicated and no tasks are missed. Option C is incorrect — the Batch API does not automatically resume interrupted processing on restart. Option D is impractical for large document sets and doesn't prevent crashes.

A Claude-based system processes financial reports in nightly batches. During a server restart at 3 AM, processing stops with only partial completion. On restart, the system must resume without reprocessing completed reports or skipping incomplete ones. Which pattern enables correct recovery?

Related Questions

Discussion