You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I am using interrupt function inside a subgraph, the first time it works as expected, it terminates the graph execution and I can type text in the console. But after I resume the graph and call interrupt for the second (or more) time, it returns the same previously cached value. So it does not work as expected.
When I remove the subgraph and impletemt the same logic inside parent graph, it works fine, so I think it is a bug, and also I found some discussions here on Github explaining this behavior and a way to fix it, hope this helps!
User answer: test answer
Execution= 1 Human message= test answer
Execution= 2 Human message= test answer
Execution= 3 Human message= test answer
Execution= 4 Human message= test answer
Execution= 5 Human message= test answer
Execution= 6 Human message= test answer
Execution= 7 Human message= test answer
Execution= 8 Human message= test answer
Execution= 9 Human message= test answer
Execution= 10 Human message= test answer
Execution= 11 Human message= test answer
Execution= 12 Human message= test answer
Execution= 13 Human message= test answer
Execution= 14 Human message= test answer
An error occurred: GraphRecursionError: Recursion limit of 25 reached without hitting a stop condition. You can increase the limit by setting the "recursionLimit" config key.
Troubleshooting URL: https://js.langchain.com/docs/troubleshooting/errors/GRAPH_RECURSION_LIMIT/
at CompiledStateGraph._runLoop (file:///C:/projects/talkapp-ai/langchain/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__/node_modules/@langchain/langgraph/dist/pregel/index.js:887:23)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async createAndRunLoop (file:///C:/projects/talkapp-ai/langchain/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__/node_modules/@langchain/langgraph/dist/pregel/index.js:980:17) {
lc_error_code: 'GRAPH_RECURSION_LIMIT',
pregelTaskId: 'd90e7254-46a7-582c-90d7-1fea82c89f52'
}
The text was updated successfully, but these errors were encountered:
Description
I am using
interrupt
function inside a subgraph, the first time it works as expected, it terminates the graph execution and I can type text in the console. But after I resume the graph and callinterrupt
for the second (or more) time, it returns the same previously cached value. So it does not work as expected.When I remove the subgraph and impletemt the same logic inside parent graph, it works fine, so I think it is a bug, and also I found some discussions here on Github explaining this behavior and a way to fix it, hope this helps!
langchain-ai/langgraph#3072
langchain-ai/langgraph@main...vigneshmj1997:langgraph:interrupt_patch_for_subgraph
As far as I understand it fixed in 0.2.63 in Python Langgraph repo
Code
Output
The text was updated successfully, but these errors were encountered: