Hi! My last question is about Conversation lifecycle / End / timeout. We’re designing a privacy-first lifecycle for our mobile app MindBend, where Botpress Conversations are temporary and eventually physically deleted. I’m trying to understand the exact lifecycle semantics of a Conversation. Our bot has an explicit product End Node that reaches the system Conversation End workflow. A few questions: Once the Conversation End workflow finishes, is that Conversation considered definitively ended? Can a new user message later be sent using the same Conversation ID? If yes, does Botpress effectively resume/reopen the same Conversation, start a new session inside it, or is the intended pattern to create a completely new Conversation? We also use inactivityTimeout: 20 with the system Timeout Workflow. When the Timeout Workflow reaches its End Node, does Botpress also execute the system Conversation End workflow? Is a timeout-ended Conversation lifecycle-equivalent to a Conversation that reached an explicit End Node? Can that same Conversation ID later receive/resume messages? I’m mainly trying to identify what Botpress considers the true terminal state of a Conversation.