langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-08-27 21:00:00 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3751] [MERGED] feat: add node timeout docs #3773

New Issue
Closed
opened 2026-06-05 18:53:06 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:53:06 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3751
Author: @open-swe[bot]
Created: 4/27/2026
Status: ✅ Merged
Merged: 5/6/2026
Merged by: @lnhsingh

Base: main ← Head: open-swe/b91256e0-0419-9881-c613-da5969fc719d

📝 Commits (3)

  • b19ddd7 Document node and functional API timeouts so users understand async-only behavior, retry handling, and timeout errors.
  • dd272b3 Merge branch 'main' into open-swe/b91256e0-0419-9881-c613-da5969fc719d
  • b677e7d Apply suggestion from @lnhsingh

📊 Changes

2 files changed (+75 additions, -4 deletions)

View changed files

📝 src/oss/langgraph/use-functional-api.mdx (+36 -4)
📝 src/oss/langgraph/use-graph-api.mdx (+39 -0)

📄 Description

Description

Adds Python LangGraph docs for configuring node and functional API timeouts after node-level timeout support was introduced. It explains async-only support, timeout errors, retries, and buffered writes. Prepared with Open SWE.

Test Plan

  • Preview the Graph API and Functional API pages and confirm timeout examples render correctly

Opened collaboratively by Sydney Runkle and open-swe.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3751 **Author:** [@open-swe[bot]](https://github.com/apps/open-swe) **Created:** 4/27/2026 **Status:** ✅ Merged **Merged:** 5/6/2026 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `open-swe/b91256e0-0419-9881-c613-da5969fc719d` --- ### 📝 Commits (3) - [`b19ddd7`](https://github.com/langchain-ai/docs/commit/b19ddd7cb33c00f307d6fe65fe7c99e886e10f7c) Document node and functional API timeouts so users understand async-only behavior, retry handling, and timeout errors. - [`dd272b3`](https://github.com/langchain-ai/docs/commit/dd272b3fba3e37c427310eb076560a37a8acaba1) Merge branch 'main' into open-swe/b91256e0-0419-9881-c613-da5969fc719d - [`b677e7d`](https://github.com/langchain-ai/docs/commit/b677e7d2fef0d54b53941371ff0f8a4be882d7d5) Apply suggestion from @lnhsingh ### 📊 Changes **2 files changed** (+75 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/langgraph/use-functional-api.mdx` (+36 -4) 📝 `src/oss/langgraph/use-graph-api.mdx` (+39 -0) </details> ### 📄 Description ## Description Adds Python LangGraph docs for configuring node and functional API timeouts after node-level timeout support was introduced. It explains async-only support, timeout errors, retries, and buffered writes. Prepared with Open SWE. ## Test Plan - [ ] Preview the Graph API and Functional API pages and confirm timeout examples render correctly _Opened collaboratively by Sydney Runkle and open-swe._ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:53:06 -04:00
yindo closed this issue 2026-06-05 18:53:06 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
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/docs#3773
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?