langgraph/cloud/concepts/api_concepts/

[giscus[bot]]

langgraph/cloud/api_concepts/

Build language agents as graphs

https://langchain-ai.github.io/langgraph/cloud/concepts/api_concepts/

[emarco177]

QQ: Is there a usecase where we would want to have multiple runs under one thread?
Can a run reference another run (under the same thread)

[hinthornw]

@emarco177 are you referring to multiple concurrent runs in one thread? or consecutive?

Consecutive runs in a thread are common! They're different turns in a conversation (run 1: user asks first question and bot response, run 2: user asks follow-up and bot resopnse, etc.). The state is updated and persisted within and after each run, so run 2 sees the graph state as it is left off after run 1. The runs "interact" via the state as loaded from checkpoints (aka "memory").

Concurrent runs gets into what we're calling "double-texting" or multi-tasking (it's basically task scheduling where you want the tasks to share context) example doc.

Basically it depends on how you want your app logic to flow.

• You can reject new runs (because you want to first finish processing this run first). This is similar to the default ChatGPT experience.
• You can interrupt the current run (and theres' nuance here about whether to roll back to the state at the run start vs. "capturing" the state at the time of interruption / start of the previous super-step).
• You can also "enqueue" the run (maybe the user just wants to ask a follow up but wants the bot to finish first, like if your bot is writing code and you want it to do another task next after it is done)

[emarco177]

WOW didn't expect such a quick answer!
Thanks for the clarification. I misunderstood the concept :)
Just as a clarification:
A graph run object is the execution of the graph with some input but not necessary from start to end nodes right?
As you mentioned with interrupts it can be paused?

[hinthornw]

That's right. The Run itself will end, but the graph may be halted with next steps / tasks to be run (in the case of interrupts). So you can create a new run with null input and it will just continue on its merry way