Gmail was not updated
Write-back is the step after the send in which Connect marks the Gmail thread read and applies your label. It is deliberately non-blocking: if it fails, the reply has already gone and is already recorded, and only the Gmail side is out of date. Nothing is lost, nothing is queued for a person, and the usual cause is a permission the mailbox no longer holds.
What you are seeing#
Inside Connect the conversation is answered and closed. In Gmail the same thread is still bold, or the label you expect is not on it. The two views disagree because they are two systems: Connect's own read state lives on the canonical thread, and Gmail's lives at Google. Write-back is the one-way bridge between them, and it runs after the reply, not before it.
That ordering is the whole design. A mailbox that cannot label is still a mailbox that can answer customers, so a labelling failure is never allowed to hold a reply. The cost of that choice is exactly the symptom on this page: a divergence you can see, rather than a delay you cannot.
Causes, most likely first#
- The mailbox no longer holds the modify permission
- Gmail write-back needs a permission beyond reading and sending. A mailbox reconnected under a narrower consent reads and sends normally and silently stops labelling.
- The mailbox is not a Gmail mailbox
- An IMAP or Microsoft mailbox has no Gmail labels. Read state may still sync; labels do not exist to apply.
- The label was renamed or deleted in Gmail
- Write-back applies a label by the name it was given. A label removed at the provider cannot be reapplied by Connect.
- A transient provider refusal
- A rate limit or a short outage. The attempt is abandoned rather than retried in a loop, because a retry storm against a mail provider is worse than a stale label.
- The mailbox disconnected after the send
- The reply used credentials that were valid at the time; the write-back a moment later found none.
What Connect completed, and what it did not complete#
| Step | State |
|---|---|
| The reply was composed and approved under the mailbox's autonomy rule | Completed |
| The send passed the compliance and allowance checks | Completed |
| The provider acknowledged the message | Completed — this is what makes it *sent* rather than uncertain |
| The canonical thread and the person's timeline were updated | Completed |
| The audit entry was written | Completed |
| The Gmail thread was marked read | Not completed |
| The Gmail label was applied | Not completed |
Nothing about the customer's experience is affected by the second half. They received the reply. What did not complete is bookkeeping inside your own Gmail account, which matters for the people working there and for nobody else.
What to do about it#
Confirm the reply actually left, on the thread in Connect.
Result A recorded acknowledgement means this is a write-back problem and not a send problem. If the state reads *uncertain* instead, you are on the wrong page.
Mark the thread read in Gmail yourself, or apply the label by hand.
Result Connect does not fight you for it; no loop will undo a manual change.
Ask an administrator to reconnect the mailbox, accepting the full set of permissions.
Result Write-back resumes on the next reply. Past threads are not retro-labelled — the step is per message, not a sweep.
The administrator's view, and escalation#
An administrator can see which provider each mailbox uses, which permissions were granted at the last consent, and the mailbox's health. Reconnecting is the whole repair for the common cause; it does not disturb conversations, drafts or history, because none of those live in the provider's copy of the mailbox.
Escalate when a Gmail mailbox has been reconnected under full consent and write-back still does not run on new replies, or when read marks apply and labels never do. Quote the mailbox address and the day; provider error text carries account and message identifiers and should not travel in a support message.
Questions#
Does a failed write-back mean the customer did not get my reply?
No. The reply is only reported as sent once the provider has acknowledged it, and write-back happens after that acknowledgement. A missing label is evidence about your Gmail account, not about delivery.
Will Connect catch up the labels later?
No. Write-back is attempted once per message, alongside the reply it belongs to. There is no background sweep that relabels history, which is why reconnecting fixes future messages and leaves past ones as they are.
Can I keep Connect out of my Gmail labels entirely?
Yes. Write-back follows the permissions the mailbox holds. A mailbox connected without the modify permission reads and sends and never touches your labels, which is the supported way to keep Connect out of your Gmail organisation.