Broadcast email statuses reference
This page describes every status a broadcast can have and what each one means for your members and your organization.
Broadcast lifecycle statuses
Section titled “Broadcast lifecycle statuses”| Status | Badge color | What it means | Can it change? |
|---|---|---|---|
| Draft | Gray | The broadcast has been saved but not sent. No emails have been dispatched. | → Queued when sent |
| Queued | Blue | The broadcast is scheduled to send and waiting for the dispatch pipeline. No emails have been dispatched yet. | → Sending, or → Cancelled if you cancel |
| Sending | Blue (animated) | The broadcast is actively dispatching to your members. Some emails may have already been delivered. | → Sent, Partial, or Cancelled |
| Sent | Green | All emails in this broadcast were dispatched successfully. | No further changes |
| Partial | Amber | Dispatching stopped before all emails were sent — for example, because the broadcast was cancelled mid-send. Some members received the email; others did not. | No further changes |
| Cancelled | Red | An admin cancelled the broadcast before it finished sending. If it was cancelled while sending, some emails may have been dispatched. See the per-recipient log for details. | No further changes |
| Failed | Red | The broadcast ended without emailing anyone. The send-detail page names why: Broadcast failed — no message was accepted (MapleGather’s email provider accepted none of the messages it attempted — each was refused or its call failed); Broadcast failed before it emailed anyone (an error in MapleGather stopped it before the email provider accepted any of its messages); Broadcast not sent — its segment has an exclusion email can’t check (the segment leaves people out by membership or event registration — remove that exclusion); Broadcast not sent — its audience couldn’t be worked out (the members it was addressed to couldn’t be worked out — create a new broadcast, and if it used a segment, first check that the segment still exists and opens); Reminder not sent — its template was taken out of use (a catch-up renewal reminder whose email template was archived or set back to draft before it went out — once the template is active again, send the catch-up reminder again); or Broadcast failed when no reason was recorded, or for a reason the page doesn’t recognize. A failed broadcast can’t be resent — create a new broadcast. If the page says “Add your organization’s postal address to send marketing email”, the broadcast started after your organization’s postal address was removed and nobody was emailed — add the address, then send again. | No further changes |
Per-recipient delivery statuses
Section titled “Per-recipient delivery statuses”These statuses appear in the recipients table on the send-detail page, one per member.
| Status | What it means |
|---|---|
| Delivered | The email reached the member’s mail server. (Delivery to their actual inbox isn’t confirmed — that depends on the member’s spam filters.) |
| Bounced | The email couldn’t be delivered. The Bounce reason column gives more detail. |
| Pending | The email is in transit. This resolves to Delivered or Bounced within a few hours. |
| Suppressed | The member was excluded from this send because they had opted out of the relevant email category before the broadcast dispatched. |
Cancellation reason codes
Section titled “Cancellation reason codes”When you cancel a broadcast, MapleGather records the reason you choose. These are the options:
| Reason code | Label shown |
|---|---|
content_error |
Mistake in content |
wrong_audience |
Wrong segment |
typo |
Typo |
regulatory |
Regulatory / consent issue |
other |
Other |