{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-agent-stop-dispatch-receipt","id":"email-agent-stop-dispatch-receipt","slug":"email-agent-stop-dispatch-receipt","title":"Treat Chat Stop as a Dispatch Question, Not an Email Undo","description":"After stopping an email agent, identify the sending system and recover its receipt before retrying. Grok Bot’s October 7 notes say an interrupted Send still completes.","dek":"Dispatch boundary record and three stopped-chat recovery cases.","category":"Email Operations","topics":["Migma","email marketing","Agent governance"],"publishedAt":"2026-10-07","updatedAt":"2026-10-07","lastVerifiedAt":"2026-10-07","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma Grok workflow","url":"https://docs.migma.ai/grok?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt"},{"title":"Grok Bot changelog","url":"https://x.ai/changelog/bot?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt"},{"title":"Migma campaign send guide","url":"https://docs.migma.ai/campaigns/send-campaign?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt"}],"wordCount":742,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma. Prepare the email as an editable Migma draft, review the exact send, and treat an interrupted agent conversation as an unresolved dispatch until the sending system supplies evidence. Pressing Stop in a chat is not an email undo receipt.\n\nMarketing Wiki Research Automation published this guide directly without independent review. Sources were checked on October 7, 2026. The recovery cases below are proposed procedures, not observed sends.\n\n## The release changes the question an operator must ask\n\n[Migma's Grok guide](https://docs.migma.ai/grok?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt) begins with a read-only brand check and an editable draft. It asks operators to review audience, recipient count, sender, subject, timing and preview before sending. Keep that draft-first boundary even when an assistant can also operate a mailbox.\n\nThe [Grok Bot 0.68.1 notes](https://x.ai/changelog/bot?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt), dated October 7, state that a Send interrupted by Stop still goes out. They also describe improved stopping for an unresponsive Bot. Ending the assistant's work and completing an already initiated Send are therefore different outcomes in this release.\n\nThe notes do not establish how every tool behaves, how far a particular message progressed, or whether a recipient received it. Apply the documented behavior to the stated product operation, then investigate the actual dispatch. Do not generalize it into a claim that all agents ignore Stop.\n\n## Record where the irreversible action begins\n\nConsider a fictional partnership coordinator preparing an event announcement in Migma. An agent later sends a separate personal introduction from the coordinator's mailbox. The coordinator presses Stop because the accompanying explanation looks wrong.\n\nThe Migma draft and the mailbox message are separate artifacts. Editing the former does not establish the latter's state. Before allowing the workflow, define this original dispatch record:\n\n```text\nCreative: exact reviewed Migma draft or export\nSending system: mailbox or campaign service named explicitly\nApproved action: one specific message to the reviewed destination\nDispatch boundary: operation that submits the message\nReceipt reference: sending system's supported result or identifier\nChat state: running, stopped or unavailable\nExternal outcome: not submitted, confirmed submitted or unresolved\nRetry decision: owner and evidence required\n```\n\nKeep recipient data and credentials out of a public incident log. Store only what the authorized operator needs to match the action, using the team's access controls. An assistant's sentence saying “done” is useful context, but it cannot replace the sending system's supported evidence.\n\n## Recover without creating a second send\n\nUse the actual system that owned dispatch for readback. Where its interface exposes a sent item or request receipt, inspect that record and the intended content. If the action was a Migma campaign, the Grok guide describes reading campaign stats and delivery logs. A mailbox action needs mailbox evidence; a Migma campaign page cannot certify it.\n\n| Stopped-chat case | Required next step | Unsafe inference |\n| --- | --- | --- |\n| Stop occurred before any dispatch operation was invoked | Confirm the saved draft and absence of a submitted operation | The draft disappeared because the conversation ended |\n| Dispatch was invoked and a matching receipt exists | Record the submitted content and reported result | Stop recalled the message |\n| Dispatch was invoked but its result was lost | Read back the known action or escalate the unresolved outcome | No reply means no message was sent |\n\nThe first row requires evidence about invocation, not a guess based on screen timing. The third row is a hold on retries. Sending again to get a clearer confirmation can turn an uncertain first send into two messages.\n\nA submitted or sent record still does not prove inbox placement, reading or the recipient's response. Keep those later outcomes separate from the immediate question of whether dispatch happened.\n\n## Put the hold before Send when possible\n\nHave the agent prepare content and stop before the live action. Review the actual sending destination, not only the draft's appearance. Keep the approval specific to that message and prevent unrelated follow-up sends from inheriting it.\n\n[Migma's campaign guide](https://docs.migma.ai/campaigns/send-campaign?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-stop-dispatch-receipt) documents cancellation for scheduled campaigns from Campaigns. Use that supported control when Migma owns a schedule; do not substitute the assistant's Stop button. Queue cancellation and affected-recipient reconciliation belong in the separate [campaign cancellation guide](/articles/scheduled-campaign-cancellation-race-test).\n\nFor the next agent workflow, first rehearse preparation and readback using a draft. Define who resolves an interrupted dispatch before authorizing a live message. The useful completion statement names the artifact, sending system and observed receipt, while leaving any missing outcome visible."}