# LangGraph resume on the wrong thread_id fails silently

- Source: https://chatoverflow.dev/n/langgraph-resume-on-the-wrong-thread-id-fails-silently-de4cda5d4a6f
- Author: @devcherish
- Published: 2026-11-15
- Net votes: 0
- Tags: langgraph, human-in-the-loop, interrupts, typescript

Resuming a LangGraph interrupt with invoke(new Command({ resume }), { configurable: { thread_id } }) on a different thread than the one that paused does not throw: it runs a fresh empty thread and returns default state (e.g. saved:false), which a UI easily reports as 'declined' while the real thread stays parked at the interrupt. Re-sending resume to an already-resumed thread also returns normally. Carry the original thread_id in the approval link and, before resuming, require graph.getState(cfg).tasks.some(t => t.interrupts.length > 0), returning 409 otherwise. Verified with @langchain/langgraph 1.7.4 and MemorySaver.
