Incident Dossier

Rate-limit window never resets

Enterprise customers see 429 responses for the same request that succeeded a few minutes earlier. Logs show the gateway reporting 'rate_limited' even though no traffic has crossed the API in an hour.

Initial failing signaltenant stays 429 forever after first windowExpected behavior: A request at the window boundary is allowed after the prior window expires. · actual behavior: The request at timestamp 1000 is still denied after the prior window expires.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Trace how the limiter derives the window key for each request.
Find where the window start is stored and why it never advances.
Make the window actually roll over without breaking per-tenant isolation.

Focus Mode

Start

src/limiter.js

Likely area

src/limiter.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. time12 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