Incident Dossier

Timeout Not Cleared on Success

During a slow upstream incident, the team noticed that some requests were being aborted with TimeoutError even though the upstream logs showed the requests completing in time. The pattern was particularly strange because the aborts clustered around requests that had already returned earlier in the day, suggesting a shared timer resource was firing into unrelated calls.

Initial failing signalSuccess-path timer still active after request resolvesExpected behavior: success-path timer is canceled · actual behavior: success-path timer is still armed and fires later

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect requestWithTimeout and follow the success path.
Notice that the scheduled timer is never canceled when the operation resolves.
Make the smallest correction so the timer is always canceled exactly once per request.

Focus Mode

Start

src/request.js

Likely area

src/request.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