Symptom
Passing an AbortSignal in config to a LangGraph.js graph doesn't cancel the run as expected.
Evidence what you'll see
- Reporter's graph got stuck after __start__ once a signal was added
- Aborting does not stop nodes that are already running
- Subgraphs don't see the parent's signal
Cause
The signal wasn't composed and passed down to nodes and subgraphs correctly, so aborting the outer run didn't reach the work in progress.
Fix steps
0 of 2 done
Your check marks stay in this browser only.
Verify the fix worked
- Start a run, abort the controller, and confirm the run stops and nodes see signal.aborted.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it