A Runbook for Email-Driven Automation

说明与用途

本运行手册通过定义运行合同、租用邮箱、收集证据以及使用决策树进行重试，建立了基于电子邮件的自动化边界，从而降低了不稳定性并简化了故障诊断。

问题

Email-driven automation failures are often blamed on slow email, but the real issues are missing boundaries around inputs, mailbox, observations, and cleanup.

结果

The runbook introduces explicit boundaries and evidence collection, turning invisible resource collisions into visible state transitions and enabling deterministic failure analysis.

工作流

• Define a run record with run_id, scenario, mailbox_id, expected_kind, created_at, expires_at
• Attach run_id as a correlation value in headers or metadata
• Reserve a unique mailbox or enforce ownership on a shared mailbox
• Poll the mailbox with a deadline and bounded retry budget
• Observe delivery, matching, and consumption, recording each in an evidence receipt
• Classify failures using a decision tree to decide whether to retry or fail
• Cleanup or expire the mailbox after success or failure

证据

Email is often treated as the last step in an automation workflow. A job creates an account, triggers a notification, waits for a message, and then reports success or failure.

来源

I have found a useful mental model: every email-driven run needs a small boundary around its inputs, mailbox, observations, and cleanup.

来源

Start with a small run record. It does not need to contain the email body or a full copy of every request.

来源

At the end of every run, write a receipt that is safe to keep in CI artifacts.

来源