Paginate bulk item outcomes with stable ordering
Large result lists exceed response limits and change order while the client reads them.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Pagination · Authorization
Estimated field mix
- API design50%
- Database engineering30%
- Security20%
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.
- BAPIBULK-101 · Define the difference between accepted and completed bulk work
- BAPIBULK-102 · Bound bulk request size and record counts before admission
- BAPIBULK-103 · Create bulk operations with tenant-scoped idempotency
- BAPIBULK-104 · Return per-item problems without exposing other tenant records
- BAPIBULK-105 · Checkpoint item progress without changing retry outcomes
Acceptance criteria
- Use stable operation-scoped ordering.
- Bound page sizes and cursor lifetime.
- Bind cursors to tenant, operation, and filter.
Implementation constraints
- Do not place raw item payloads in cursors.
Verification to include
- Read all outcomes without duplicates.
- Reject a cursor reused for another operation or tenant.
Deliverables
- Outcome pagination endpoint.
Rollout and recovery
Keep terminal result pages immutable within retention.
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.