# How can I implement the ability to interrupt and resume execution at any time **URL:** \ **Category:** LangGraph\ **Tags:** intro-to-langgraph, python-help\ **Created:** [November 27, 2025, 1:29am UTC](https://forum.langchain.com/t/how-can-i-implement-the-ability-to-interrupt-and-resume-execution-at-any-time/2356 "2025-11-27T01:29:54Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![CxyZyr](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/cxyzyr/32/1753_2.png) [@CxyZyr](https://forum.langchain.com/u/CxyZyr)\ **Post date:** [November 27, 2025, 1:29am UTC](https://forum.langchain.com/t/how-can-i-implement-the-ability-to-interrupt-and-resume-execution-at-any-time/2356/1 "2025-11-27T01:29:54Z")
I’m developing an agent using LangGraph. My main graph nests two subgraphs. I’ve noticed that LangGraph doesn’t natively support an interruption mechanism—by “interruption,” I mean the ability for a user to manually terminate execution at any node and immediately send a new message to continue the conversation. To address this, I’ve wrapped the execution in a Python async manager, using something similar to `asyncio.CancelledError` to cancel the ongoing run. However, when I restart the conversation, the checkpointed messages are always missing some content, making it difficult to properly restore and continue the dialogue from where it left off. I’d like the state of all nodes executed prior to termination to be preserved when the interruption occurs. Could you please explain why this is happening, or suggest a more elegant way to handle such interruptions? Thank you very much for your time—I’d greatly appreciate a prompt reply. --- _[View the full topic](https://forum.langchain.com/t/how-can-i-implement-the-ability-to-interrupt-and-resume-execution-at-any-time/2356)._