Resume a large photo upload without restarting the whole queue
One 12 MB equipment photo repeatedly fails halfway through and blocks all completed visits. Integrate the resumable-upload contract and isolate attachment progress from unrelated operations.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Resumable uploads · Fault isolation · Persistence
Estimated field mix
- Mobile40%
- Storage systems40%
- Networking20%
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
The fictional Vale facilities team services equipment in basements with poor reception. Technicians receive assigned work orders, record checks, and attach synthetic equipment photos. The practice app uses an on-device database and a stub sync service; background location tracking is excluded.
Setup prerequisites
- Synthetic work orders and a revisioned sync contract
- An emulator with controllable connectivity and app lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FIELD-102 · Commit a completed checklist item before showing it saved
- FIELD-104 · Keep photo evidence attached after the app is suspended
- FIELD-101 · Tell technicians which work orders are available offline
- FIELD-103 · Make inspection inputs usable with large text
- FIELD-105 · Explain why a work order is not ready to finish
- FIELD-106 · Drain the sync queue without duplicating completed visits
Acceptance criteria
- Committed upload offsets are persisted and reconciled with the service after reconnect.
- An expired upload session starts a new session without losing the source file.
- Failure of one attachment does not block sync for another independent work order.
Implementation constraints
- Use small synthetic chunks in tests; server file integrity and scanning remain separate responsibilities.
Verification to include
- Interrupt after two acknowledged chunks and resume from the server-confirmed offset.
- Expire the session and simulate a missing local file; show repair guidance and allow another work order to sync.
Deliverables
- Resumable upload adapter and offset/session recovery cases
Rollout and recovery
Enable for larger attachments first; pause uploads and keep staged files if offset reconciliation fails.
Value of the work
For the engineer: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows.
For the team: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment.
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.