Incident Dossier

Retry After Shutdown Stalls Quietly

During a graceful-shutdown drill the team observed the service hanging on its way out. The shutdown handler was waiting for a retry queue to drain, but the queue was retrying operations against an already-shut-down downstream. The retries eventually exhausted their budget and the queue settled, but the queued promise had rejected with the underlying upstream error rather than a shutdown signal — so callers could not distinguish 'service is gone' from 'upstream is broken'.

Initial failing signalShutdown does not cancel queued retriesExpected behavior: queued promise rejects with ShutdownSignal · actual behavior: The queued promise rejects with the original upstream error instead.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect createRetryQueue and ask whether the retry loop ever notices a shutdown.
Notice that cancelAll is a no-op and the loop has no cancellation check.
Track a controller per enqueue, set cancelled on shutdown, and have the loop bail out when it sees the flag.

Focus Mode

Start

src/shutdown.js

Likely area

src/shutdown.js

Challenge Coach

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

TopicReliability

DifficultyHard

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