Skip to content
Help Center
Sign In

Why A Draft Was Blocked Before Sending

In Chat or by voice, a staged send or draft edit can be blocked or fall through if it expires, gets superseded, or the draft is missing something dreamif.ai needs before it can send.

The staged action expired or was superseded#

When dreamif.ai stages a send or a draft edit, it's waiting for you to reply or say "confirm." If you ask for something else first, that new request replaces the staged one, and the original send never happens. A staged action also expires if it waits too long. Confirm after that and dreamif.ai answers "That staged action expired. Stage it again before continuing."

Fix: re-ask for the send. dreamif.ai stages it again, and you confirm from there.

The draft is still autosaving#

The in-chat draft editor autosaves as you type, showing "Saving…", then "Draft saved." If you see "Saving…" or "Autosave delayed," wait for "Draft saved" before you send, so the version you reviewed is the one that goes out. Open in Gmail always works regardless of autosave state; it's the send that waits.

The draft is missing what it needs to send#

Before dreamif.ai sends, it checks the draft has what it needs:

  • No recipient. You'll see "This draft needs a recipient before it can be sent." Add a recipient, then ask dreamif.ai to send again.
  • No body. An empty draft has nothing to send. Add content to the draft first.

Related articles

Understand Chat Confirmations
Sends are confirmed by the Send button. Everything else Chat wants to change is staged first and applied only after you reply confirm.
How voice confirmations work
Anything that changes your Gmail, calendar, contacts, or settings is staged first. Say "confirm" to let it through, or press Send in the draft panel. There's no pop-up dialog to click.
Why A Nurture Draft Could Not Be Sent
dreamif.ai re-checks a nurture touchpoint right before it sends. Here is what each block message means and how to fix it.