langchain-ai/langgraphjs
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraphjs.git synced 2026-07-22 09:05:28 -04:00
Code Issues 108 Packages Projects Releases 20 Wiki Activity

suggestion: add a property to recognize whether the graph instance is interrupted #148

New Issue
Closed
opened 2026-02-15 17:16:19 -05:00 by yindo · 2 comments
yindo commented 2026-02-15 17:16:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @vianvio on GitHub (Dec 23, 2024).

Thanks for the great update of implementing intrerrupt and Command resume, I have integrated these features in my app, but found it unclear to figure out whether the instance is interrupted.

currently I'm using next node for check

const nextNode = (await flowInstance.getState(config)).next;
if (Array.isArray(nextNode) && nextNode.length > 0) {
  // do something
}

and I find the test case is using number of tasks on state for check

const currTasks = (await graph.getState(config)).tasks;
expect(currTasks[0].interrupts).toHaveLength(1);

Both should work but not good I think, can we have a property like isInterrupted or interruption: true, that would be more friendly to use

Originally created by @vianvio on GitHub (Dec 23, 2024). Thanks for the great update of implementing intrerrupt and Command resume, I have integrated these features in my app, but found it unclear to figure out whether the instance is interrupted. currently I'm using next node for check ``` const nextNode = (await flowInstance.getState(config)).next; if (Array.isArray(nextNode) && nextNode.length > 0) { // do something } ``` and I find the test case is using number of tasks on state for check ``` const currTasks = (await graph.getState(config)).tasks; expect(currTasks[0].interrupts).toHaveLength(1); ``` Both should work but not good I think, can we have a property like isInterrupted or interruption: true, that would be more friendly to use
yindo closed this issue 2026-02-15 17:16:19 -05:00
yindo commented 2026-02-15 17:16:20 -05:00
Author
Owner
Copy Link
Copy Source

@jacoblee93 commented on GitHub (Jan 3, 2025):

Hey @vianvio, I think what you're doing is fine for now!

Some computed method could be nice in the future, so will leave this open.

@jacoblee93 commented on GitHub (Jan 3, 2025): Hey @vianvio, I think what you're doing is fine for now! Some computed method could be nice in the future, so will leave this open.
yindo commented 2026-02-15 17:16:20 -05:00
Author
Owner
Copy Link
Copy Source

@dqbd commented on GitHub (Jun 17, 2025):

We now return the interrupts in state with @langchain/langgraph 0.3.x!

@dqbd commented on GitHub (Jun 17, 2025): We now return the interrupts in state with `@langchain/langgraph 0.3.x`!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
checkpointer
docs-needed
documentation
enhancement
good first issue
good writeup
help wanted
invalid
langgraph-supervisor
open-swe-auto
platform
prebuilt
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs#148
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?