Retry partial attachment removal without forgetting derived copies
The primary object is gone but thumbnail removal timed out. A retry treats the missing primary as success for the entire attachment.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Idempotency · Partial failure
Estimated field mix
- Privacy engineering40%
- Distributed systems30%
- Storage 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 support service keeps uploaded diagnostic files indefinitely. The exercise policy expires attachments 30 days after case closure, while a separately authorized investigation hold pauses removal. These are invented product rules, not legal advice or compliance certification.
Setup prerequisites
- Create synthetic cases, attachment metadata and a fake object store with controllable failures.
- Use an injected UTC clock and an authorized operator fixture; no real support uploads are needed.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- RRETENTION-101 · Calculate attachment expiry from the case closure instant
- RRETENTION-102 · Inventory every storage location used by one support attachment
- RRETENTION-103 · Require scoped authority to place an attachment on investigation hold
- RRETENTION-104 · Preview the attachment purge set with stable decision reasons
- RRETENTION-105 · Recheck holds when a queued attachment purge begins
Acceptance criteria
- Track per-location progress and idempotent removal outcomes.
- Distinguish not-found from authorization and transport failure.
- Mark the purge complete only when every required location is confirmed or an explicit unresolved exception remains.
Implementation constraints
- Keep evidence of unresolved copies in restricted operational records; do not expose storage credentials in failure text.
Verification to include
- Fail thumbnail removal after primary success, retry and verify both locations are reconciled.
- Inject a forbidden response and confirm it remains unresolved rather than being treated as already absent.
Deliverables
- Per-location purge state and partial-failure regressions
Rollout and recovery
Retry only incomplete locations; stop promotion when a provider cannot give a trustworthy deletion outcome.
Value of the work
For the engineer: Practice temporal policy, deletion races, exception authority and truthful recovery reporting.
For the team: Develop inspectable retention behavior that a company can review against its own approved data policy.
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.