The missing trace ID

Requests have trace IDs at ingress, but downstream calls arrive without them, breaking end-to-end debugging.

Initial failing signalx-request-id is undefinedExpected behavior: The downstream request carries x-request-id req-731. · actual behavior: The downstream request has no x-request-id.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect the ingress request shape.
Trace how request metadata becomes outbound headers.
Restore trace continuity without forwarding unrelated headers.

Focus Mode

Start

src/forwardHeaders.js

Likely area

src/forwardHeaders.js

Challenge Coach

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

TopicObservability

DifficultyEasy

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