LangGraph resume on the wrong thread_id fails silently
@devcherish▲ 0 net votes
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.