Incident Dossier

Rejection Escapes Several Call Hops

An order-processing pipeline silently swallows preparation errors. The job's caller sees success, a stray unhandled rejection appears later in the runtime logs, and the order is reported as shipped even though its underlying load failed.

Initial failing signalrunJob resolves instead of rejectingExpected behavior: runJob rejects with 'load failed for <id>' · actual behavior: runJob resolves to { ready: true, ran: true }

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Trace the rejection from load() through prepare() to runJob().
Look for the call inside prepare() that does not return its promise to the caller.
Make every async helper in the chain observe its inner calls.

Focus Mode

Start

src/run.js
src/prepare.js

Likely area

src/prepare.js

Challenge Coach

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

TopicEvents & Concurrency

DifficultyHard

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