A bare ToolNode.invoke() has needed a Runtime object for eleven months

Call `ToolNode.invoke()` outside a compiled graph and nothing injects the runtime context, so the node raises `ValueError: Missing required config key 'N/A' for 'tools'` ^[4]. Neither string in that message names the argument you now have to supply. A required parameter whose absence reports itself as config key `'N/A'` is not going to be found by grep. The repair is one import and one keyword: `Runtime` from `langgraph.runtime`, passed as `runtime=Runtime()` with no arguments, which gives the node its context without standing up a graph ^[5].

The async `TypeError` is the same change seen from the other side. LangGraph hands `runtime` as a keyword argument to every callable it invokes, so a custom coroutine whose signature does not accept it dies at the call ^[6]. That one is fixed in your signature, not at the call site: `**kwargs` absorbs `runtime` and whatever gets injected next ^[7]. Three of the four documented failure modes have a caller-side fix along those lines ^[2], but the cancellation path is the holdout: `asyncio.CancelledError` propagates through `ToolNode` uncaught when timeout logic cancels a task, your cleanup code never runs, and it shows up as flaky tests under load ^[10]. Until the upstream fix lands, the postmortem offers only defensive wrapping of tools that hold sockets or file handles in `try/except asyncio.CancelledError` ^[11].

Two instructions in the same writeup do not agree, and the disagreement is worth resolving before you copy either. The prose says pin the minor version, on the grounds that this project has a history of breaking changes on minor bumps ^[15]. The dependency block sets `langgraph = ">=1.0.2"` and `langgraph-prebuilt = ">=1.0.2"` with no upper bound and a comment that it is verified working through 1.2.11 ^[14]. The pin advice and the open-ended dependency block describe two different policies ^[3]. The floor is the defensible half, because it is what the `runtime=` and `handle_tool_errors=` fixes require. The missing ceiling is only safe if you are running the suite that would catch the next injected parameter, which is precisely the suite that broke here.

About eleven months separate the October 2025 change from the September 2026 check that the two issues are still open against 1.2.11 ^[1]. At that duration, `Runtime()` in a test is not a workaround waiting on a release; it is the entry point, and the postmortem says as much ^[13].

The material is silent on maintainer intent: nothing here states whether the `handle_tool_errors` default reverting to `False` was deliberate or a regression, and there is no fix timeline for the cancellation path. The scope of exposure is also narrower than the error list suggests: the `ValueError` fires only when the node is invoked outside a compiled graph ^[4], so a suite that exercises the compiled graph end to end never sees it and inherits the default flip alone, quietly ^[4].