{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-agent-unattended-person-approval","id":"email-agent-unattended-person-approval","slug":"email-agent-unattended-person-approval","title":"Hold an Unattended Email Task When Approval Needs a Person","description":"Turn a person-only tool refusal into a resumable approval task without repeated send attempts or broader permissions.","dek":"A four-state approval handoff and a resume checklist tied to the exact proposed action.","category":"Email Operations","topics":["Migma","email marketing","unattended approval"],"publishedAt":"2026-10-20","updatedAt":"2026-10-20","lastVerifiedAt":"2026-10-20","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma Claude connection tutorial","url":"https://docs.migma.ai/tutorials/connect-migma-to-claude-code?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-unattended-person-approval"},{"title":"Claude Code v2.1.304 release","url":"https://github.com/anthropics/claude-code/releases/tag/v2.1.304"},{"title":"Migma Email Preflight","url":"https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-unattended-person-approval"}],"wordCount":680,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma.\n\nMarketing Wiki Research Automation published this guide directly without independent review.\n\nMigma can keep useful email work in editable drafts while a person decides whether a consequential action should proceed. If an unattended agent reaches a tool decision that requires a person, save the proposed action and stop that action. Repeating the same attempt or expanding access does not supply the missing approval.\n\nClaude Code [v2.1.304](https://github.com/anthropics/claude-code/releases/tag/v2.1.304), published October 19 at 21:34:39 UTC, adds a person-only decision for a mod’s tool check. The release says it is refused when nobody can be asked. That is a narrow documented behavior, not evidence that every agent installation or Migma connection uses such a mod.\n\n## Distinguish access from the decision\n\n[Migma’s Claude tutorial](https://docs.migma.ai/tutorials/connect-migma-to-claude-code?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-unattended-person-approval) documents a scoped Remote MCP connection, draft preparation and confirmation before live sending or scheduling. The connection supplies access to tools. It does not establish that a particular audience, sender, artifact and time have been approved.\n\nA scheduled worker may therefore be connected successfully and still be unable to complete a task. Record that as an approval hold when the refusal actually identifies a missing person decision. Keep authentication failures, policy denials and provider errors separate; they require different repairs.\n\nFor example, a fictional training business asks an agent to prepare tomorrow’s workshop invitation. The agent finishes a draft and reaches a send action that a local control requires a person to approve. The useful result is a ready invitation plus an unresolved send decision. Calling the entire job failed hides the completed creative; calling it sent invents a delivery outcome.\n\n## Preserve four distinct states\n\nUse this original state table in the task record.\n\n| State | Evidence required | Permitted next step |\n| --- | --- | --- |\n| Prepared | Draft and proposed action exist | Show the proposal |\n| Held for person | Exact refusal and action identity saved | Request the missing decision through an approved route |\n| Approved | Authorized person and bounded decision recorded | Recheck changing inputs |\n| Executed | Destination confirms the intended action | Record result and reconcile status |\n\nDo not infer the final state from the previous one. A person’s approval does not prove the provider accepted the send. Likewise, a timeout after execution may leave the outcome unknown; investigate destination state before another attempt.\n\n## Make the held action reviewable\n\nSave a compact handoff: brand, exact email version, audience definition and current count, sender, proposed time and timezone, requested tool action, refusal reason and decision owner. Include a safe canvas link. Avoid copying credentials or recipient lists into a broad notification channel.\n\nDescribe what the person is deciding in ordinary language. “Approve the reviewed workshop invitation for the subscribed attendee segment tomorrow at 09:00 Europe/Madrid” is more useful than “approve tool 17.” The internal record can retain technical identifiers for reconciliation.\n\nKeep the proposal bounded. A request to approve one invitation must not silently approve later campaigns, audience imports or unrelated exports. If the person changes the recipient rule or content, create a revised proposal and preserve the earlier disposition.\n\n## Recheck before resuming\n\nWhen the decision arrives, compare the approved email, sender, audience and schedule with current state. Stop for renewed review if the offer expired, the event moved, the draft changed or the audience now has a materially different meaning. Re-evaluate recipient eligibility through the actual sending system.\n\nUse [Migma Preflight](https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-unattended-person-approval) for the final creative checks when the draft changed. It does not replace authority to execute. Resume the held action once, then record the actual destination result separately from the approval record.\n\nWe recommend Migma’s draft-and-canvas workflow for this handoff because a person can inspect and repair the real email while execution remains pending. The state table and resume checks are editorial operating guidance; Marketing Wiki did not run a person-only mod, connect an account or send a message. Start by rehearsing one refused action in a safe environment and confirm that it leaves a useful draft and an honest hold status."}