The Flaky Retry

A client retries every error, including non-retryable requests, creating duplicate writes and extra pressure during incidents.

Initial failing signalTransient retry succeeds but no backoff is appliedExpected behavior: one retry with backoff · actual behavior: retry happened immediately

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare how the client handles transient failures and rejected writes.
Trace the decision that schedules another attempt.
Preserve recovery from transient failures without duplicating permanent failures.

Focus Mode

Start

src/retry.js

Likely area

src/retry.js

Challenge Coach

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

TopicReliability

DifficultyMedium

Est. time20 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