Checkpoint item progress without changing retry outcomes
A worker restart reapplies successful items and duplicates side effects.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Batch processing · Idempotency
Estimated field mix
- Data engineering40%
- Database engineering30%
- Distributed systems30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional catalog API needs to accept imports too large for one synchronous request. Partners need to distinguish accepted work, completed items, and recoverable failures.
Setup prerequisites
- Create a local API and worker double with synthetic catalog records and controlled interruption points.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Persist committed item outcomes with operation identity.
- Resume only incomplete items.
- Return the original result for exact processed-item replay.
Implementation constraints
- Bound item batches and transaction duration.
Verification to include
- Interrupt after a committed batch and resume.
- Retry a successful item and verify unchanged effects.
Deliverables
- Resumable bulk processor.
Rollout and recovery
Retain checkpoints and immutable terminal item outcomes.
Value of the work
For the engineer: Practice asynchronous resource contracts, partial outcomes, and idempotent operations.
For the team: Provide predictable bulk integration behavior without ambiguous success or repeated effects.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.