---
title: "Comment by Ehsan on \"Designing AI Email Automation That Does Not Fail Silently\" | Hashnode"
description: "Treating the model draft as untrusted input and re-checking state right before send is the part most n8n demos skip. How are you logging those failed transition"
url: "https://hashnode.com/posts/designing-ai-email-automation-that-does-not-fail-silently/6b00c7d11424e215a465966c/comment/6b016060d285b0ba8e333636"
---

[Discussion](https://hashnode.com/posts/designing-ai-email-automation-that-does-not-fail-silently/6b00c7d11424e215a465966c)

Comment [Designing AI Email Automation That Does Not Fail Silently](https://hashnode.com/posts/designing-ai-email-automation-that-does-not-fail-silently/6b00c7d11424e215a465966c)

[Ehsan](https://hashnode.com/@ibuildinpublic)

[1h ago](https://hashnode.com/posts/designing-ai-email-automation-that-does-not-fail-silently/6b00c7d11424e215a465966c/comment/6b016060d285b0ba8e333636)

Treating the model draft as untrusted input and re-checking state right before send is the part most n8n demos skip. How are you logging those failed transitions so a human can resume without sending a second reply?
