The workflow is aborted when the time is over 300s in node and the 'step_timeout' param doesn't work #300

Closed
opened 2026-02-15 18:15:37 -05:00 by yindo · 2 comments
Owner

Originally created by @oneWalker on GitHub (Jul 9, 2025).

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangGraph.js documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangGraph.js rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package).

Example Code

Here is the pseudocode;

 const compiledWorkflow = this.workflow.compile({
      checkpointer: this.checkpointer,
    });
 compiledWorkflow.stepTimeout = 1000 * 60 * 60; //1 hour but it doesn't work. The run will be aborted when single node is over 300s;
 await compiledWorkflow.invoke();

Error Message and Stack Trace (if applicable)

nvoke:error:nodecode-1751965386018 Error: Aborted
at EventTarget.listener (/root/node_modules/@langchain/core/dist/utils/signal.cjs:20:24)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20)
at EventTarget.dispatchEvent (node:internal/event_target:755:26)
at abortSignal (node:internal/abort_controller:370:10)
at node:internal/abort_controller:373:20
at Set.forEach ()
at abortSignal (node:internal/abort_controller:371:30)
at AbortController.abort (node:internal/abort_controller:392:5)
at EventEmitter. (/root/apps/flow-app/dist/domain/service/langgraph/core/event-manager.service.js:12:24)
at EventEmitter.emit (/root/node_modules/eventemitter2/lib/eventemitter2.js:1008:19)

Description

The workflow is aborted when the time is over 300s in node and the 'step_timeout' param doesn't work.

  1. dont set the step_timeout. The result is that the workflow is aborted when it's over 300 seconds.
  2. set the step_timeout to avoid the potential step_timeout limitation. The result is the same that it's aborted by langgraphjs system.

System Info

Platform:(macos, linux/amd64)
Node version: v20.18.0

Originally created by @oneWalker on GitHub (Jul 9, 2025). ### Checked other resources - [x] I added a very descriptive title to this issue. - [x] I searched the LangGraph.js documentation with the integrated search. - [x] I used the GitHub search to find a similar question and didn't find it. - [x] I am sure that this is a bug in LangGraph.js rather than my code. - [x] The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package). ### Example Code Here is the pseudocode; ```js const compiledWorkflow = this.workflow.compile({ checkpointer: this.checkpointer, }); compiledWorkflow.stepTimeout = 1000 * 60 * 60; //1 hour but it doesn't work. The run will be aborted when single node is over 300s; await compiledWorkflow.invoke(); ``` ### Error Message and Stack Trace (if applicable) nvoke:error:nodecode-1751965386018 Error: Aborted at EventTarget.listener (/root/node_modules/@langchain/core/dist/utils/signal.cjs:20:24) at [nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20) at EventTarget.dispatchEvent (node:internal/event_target:755:26) at abortSignal (node:internal/abort_controller:370:10) at node:internal/abort_controller:373:20 at Set.forEach (<anonymous>) at abortSignal (node:internal/abort_controller:371:30) at AbortController.abort (node:internal/abort_controller:392:5) at EventEmitter.<anonymous> (/root/apps/flow-app/dist/domain/service/langgraph/core/event-manager.service.js:12:24) at EventEmitter.emit (/root/node_modules/eventemitter2/lib/eventemitter2.js:1008:19) ### Description The workflow is aborted when the time is over 300s in node and the 'step_timeout' param doesn't work. 1. dont set the step_timeout. The result is that the workflow is aborted when it's over 300 seconds. 2. set the step_timeout to avoid the potential step_timeout limitation. The result is the same that it's aborted by langgraphjs system. ### System Info Platform:(macos, linux/amd64) Node version: v20.18.0
yindo added the bugquestion labels 2026-02-15 18:15:37 -05:00
yindo closed this issue 2026-02-15 18:15:37 -05:00
Author
Owner

@dqbd commented on GitHub (Jul 9, 2025):

Hello @oneWalker! We're currently not setting the 300s timeout anywhere in the code. Can you create a minimal, reproducible example demonstrating the timeout?

@dqbd commented on GitHub (Jul 9, 2025): Hello @oneWalker! We're currently not setting the 300s timeout anywhere in the code. Can you create a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) demonstrating the timeout?
Author
Owner

@oneWalker commented on GitHub (Jul 9, 2025):

@dqbd
I really appreciate that you addressed the issue. After my serious checking, it's caused by a network problem in k8s's some system. I'm sorry and thank you again

@oneWalker commented on GitHub (Jul 9, 2025): @dqbd I really appreciate that you addressed the issue. After my serious checking, it's caused by a network problem in k8s's some system. I'm sorry and thank you again
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs#300