The draft is still waiting

What the symptom looks like#

The reply exists. You can read it on the thread. It has not gone anywhere, and nothing on the conversation itself explains why. That is the whole difficulty: a held reply and a reply waiting for a person look almost identical on Conversations, and the difference is on another screen.

The four holds, and where each one shows#

The diagnosis, stage by stage#

1. Trigger — somebody notices a written reply that has not been sent.
2. User or external event — none; the customer's message arrived normally and was answered in writing.
3. Authentication and workspace resolution — the thread, the mailbox and the rules all belong to one workspace and are read inside it.
4. Ingest — the reply already exists as a record, which is why it can be held at all.
5. Canonical record — nothing changes while it waits; the text you approve is the text that goes.
6. Classification — identify which of the four holds applies; they are evaluated in a fixed order.
7. Knowledge, memory and rules — a block:email directive is a fifth reason a reply may never have been written; that is a different symptom, because no draft exists.
8. Autonomy and approval — the hold is resolved by a person deciding, by a mode changing, or by capacity returning.
9. Action through a provider — on release, the send runs through the same boundary a person's own send uses.
10. Result — sent with provider evidence, or held again by the next reason in the order.
11. Relationship, timeline and memory — the reply lands on the timeline when it goes, not when it was written.
12. Audit, usage and Needs You — the release is recorded against the person who made it, which is what answers 'who let this go out' months later.

What Connect did complete#

• The message was read, triaged and answered in writing, grounded in the workspace's own knowledge.
• The compliance checks ran, so a reply that is merely held has not also failed a suppression check.
• The hold is recorded as a decision, with the rule that caused it.
• Where the hold is one a person can clear, the item was ranked into Needs You rather than left to be found.

What Connect did not complete#

• Nothing was sent. No provider has seen the message, there is no copy in the sent folder, and no delivery was attempted.
• The thread is not closed, and the commitment inside the reply is not yet a follow-up.
• No write-back happened, so the original still reads as unanswered at Gmail.
• Under draft_only, nothing was queued for anybody — that mode deliberately does not even ask.

What you can do, and when to escalate#

1. Open Needs You first and look for the thread.

   Result If it is there, this is an approval, and approving sends it immediately.

2. If it is not there, check the autonomy mode at the contact, the mailbox, the channel and the workspace, in that order.

   Result The narrowest rule wins, so the workspace setting can be entirely irrelevant.

3. Check Plan and Usage.

   Result A spent allowance holds an approved send without any further signal on the thread.

4. Check the recipient's record for a suppression.

   Result The origin of the entry is shown, which is what tells you whether it may be cleared.

An administrator can change the autonomy mode for the scope that is holding replies, review whether the approval queue has an owner during working hours, and check whether the plan's allowance matches the volume the workspace actually handles. Escalate when none of the four holds applies and the reply still does not move — that is not a hold, and the useful evidence is the thread, the mailbox and the time it was written.

Questions#

Related#

• Held drafts
• Approving and rejecting a draft
• What Connect may do
• The daily email allowance
• The recipient is suppressed
• Drafting and approving a reply, end to end
• Human approval without blocking low-risk work