Pagination filter applied after the slice Debugging Lab

Pagination filter applied after the sliceData IntegrityHardPreparing workspaceAutosaved

00:00

Incident Dossier

Pagination filter applied after the slice

Support receives reports that paginating `GET /orders?status=paid` returns too few rows on each page and that some paid orders never appear at all. The bug shows up three call-hops from the route: route handler → listOrders → buildQuery → paginate/applyFilters.

Initial failing signalpaid page returns mixed statuses and missing rowsExpected [1, 3, 5] · received [1, 3] with row 5 missing on page 1

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Trace the call chain from the route handler down to the query builder.
Notice the order of `paginate` and `applyFilters` in the composed builder.
Re-order them so the filter narrows the dataset before the slice.

Focus Mode

Start

src/router.js
src/orders.js
src/query.js

Likely area

src/query.js
src/orders.js
src/router.js

Progressive hints

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicData Integrity

DifficultyHard

Est. time25 min

Workspacecreating

Explorer

Preparing workspace files…

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ workspace boot

Workspace booting...