Idempotency key trimmed too much Debugging Lab

Idempotency key trimmed too muchAPI & Request FlowEasyPreparing workspaceAutosaved

00:00

Incident Dossier

Idempotency key trimmed too much

Mobile retries with the same idempotency header still produce fresh payments. The header is reaching the handler intact, but the dedupe layer forgets it as soon as the request is logged.

Initial failing signalRetry returns no cached responseExpected store.lookup(rawKey) returns the stored response · received store.lookup(rawKey) returns null

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Call store.remember with a real-looking idempotency key, then store.lookup with the same key.
Compare the key each side derives from the raw header.
Make the reader and writer agree on the same canonical key.

Focus Mode

Start

src/key.js

Likely area

src/key.js

Progressive hints

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

TopicAPI & Request Flow

DifficultyEasy

Est. time12 min

Workspacecreating

Explorer

Preparing workspace 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$ workspace boot

Workspace booting...