From 17f4bbfa0317a1b8d8755a3c9af7e2b693e5d3db Mon Sep 17 00:00:00 2001 From: Chang Jia Geng Date: Thu, 2 Oct 2025 15:53:07 +0800 Subject: [PATCH] minor format edits Fix indentation for points 3 and 4 under TroubleShooting --- build/oss/javascript/langgraph/INVALID_CHAT_HISTORY.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/build/oss/javascript/langgraph/INVALID_CHAT_HISTORY.mdx b/build/oss/javascript/langgraph/INVALID_CHAT_HISTORY.mdx index 7977b1a90..b67b7f7ba 100644 --- a/build/oss/javascript/langgraph/INVALID_CHAT_HISTORY.mdx +++ b/build/oss/javascript/langgraph/INVALID_CHAT_HISTORY.mdx @@ -37,7 +37,8 @@ To resolve this, you can do one of the following: **NOTE**: this will append the messages to the history and run the graph from the START node. * manually update the state and resume the graph from the interrupt: 1. get the list of most recent messages from the graph state with `graph.getState(config)` - 2. modify the list of messages to either remove unanswered tool calls from AIMessages - -or add ToolMessages with `toolCallId`s that match unanswered tool calls 3. call `graph.updateState(config, {messages: ...})` with the modified list of messages 4. resume the graph, e.g. call `graph.invoke(null, config)` + 2. modify the list of messages to either remove unanswered tool calls from AIMessages + or add ToolMessages with `toolCallId`s that match unanswered tool calls + 3. call `graph.updateState(config, {messages: ...})` with the modified list of messages + 4. resume the graph, e.g. call `graph.invoke(null, config)`