Incident Dossier

Partial Success Discarded by Batch

During a partial outage, a batch import reported a single failure for one row and the operator had to rerun the entire batch from scratch, even though the other 99 rows had been written successfully. The import job's audit log showed every row being reprocessed on each retry, multiplying the load on the downstream system right when it was least able to absorb it.

Initial failing signalPartial batch throws away successful resultsExpected behavior: result.successes contains the items that succeeded · actual behavior: processBatch rejects, no successes object is reachable

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect processBatch and trace what happens after the loop collects per-item outcomes.
Notice that any non-empty errors list causes the helper to throw.
Return the structured outcome instead and let the caller decide what to retry.

Focus Mode

Start

src/batch.js

Likely area

src/batch.js

Challenge Coach

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

TopicReliability

DifficultyEasy

Est. time15 min

Workspacepreparing

Explorer

Loading 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$ prepare workspace

Preparing workspace