Outcome
You can choose the safe next action for each campaign status and avoid duplicate sends when transport may already have been attempted.
Navigation path
Email Blasts > Recent blasts
Access
Active CREBuilder subscription for new hosted sends; prior drafts and history may remain visible
On this page
Before you start
Data, sources, and access to prepare
- A submitted hosted campaign or downloaded HTML event
Use the hub as a bounded recent ledger
- 1
Open Recent blasts
Email Blasts > Recent blasts
Locate the campaign by subject, method, and date after the table finishes loading.
Expected result: The latest durable row for the campaign is visible when it falls within the latest 50.
If this does not happen: If loading fails, retry before concluding that no attempt exists.
- 2
Confirm method and historical provider label
Recent blasts > campaign row
Read whether the event used CREBuilder Mail, Download HTML, or a retained legacy provider label.
Expected result: You understand the delivery boundary represented by the row.
If this does not happen: Do not expect a legacy label to be available as a current send method.
- 3
Read status and available detail
Recent blasts > status and detail
Read the status, recorded sent count, durable suppression count, and any broker-safe partial, review, reconciliation, or refusal reason. On mobile, critical warning detail repeats below the subject before the horizontally scrollable Status column.
Expected result: The next action follows the evidence that the row actually exposes.
If this does not happen: A Sent row does not expose a failed-recipient list or restricted operator evidence. Do not infer complete recipient outcomes from the Sent label.
Choose the correct action for every status
| Visible status | Meaning | Safe next action |
|---|---|---|
| Sent | One or more transport attempts were accepted or durably recorded. | Compare the recorded sent count with the effective audience you recorded at preflight. Do not claim inbox placement, opens, or clicks. |
| In review | The campaign is held and will send only after approval. | Wait for approval or rejection. Do not submit another copy. |
| Sending | Delivery is in progress or confirmation is still settling. | Wait and refresh history later. Do not resend. |
| Outcome unconfirmed | The system cannot yet prove whether transport occurred. | Do not resend. Preserve the operation and wait for reconciliation or contact support. |
| Rejected | Review did not approve the campaign and it was not sent. | Read the reason, correct the underlying issue, and create a new submission only when appropriate. |
| Failed | The attempt reached a terminal failure state. | Read the reason and verify whether the UI explicitly permits a corrected new attempt. |
| Downloaded | HTML was generated locally. | Import it into the external platform and complete audience, compliance, scheduling, and delivery there. |
| Draft created | A retained legacy workflow created a provider draft. | Treat it as historical. A draft is not sent. |
Never work around uncertainty with a duplicate send
Sending and Outcome unconfirmed are the two critical states where a provider attempt may already exist. Wait for durable reconciliation or obtain support guidance.
Recognize possible partial results and CRM activity projection
Eligible recipient attempts become contact activity
Suppression removes protected addresses before transport. Each remaining recipient attempt is reconciled before the CRM timeline records blast_sent.
Hosted campaign operation
Authoritative suppression check
Separate recipient attempts
Accepted attempt
Failed recipient attempt
Idempotent blast_sent contact activity
- Hosted campaign operationAuthoritative suppression check
- Authoritative suppression checkSeparate recipient attempts
- Separate recipient attemptsAccepted attempt
- Separate recipient attemptsFailed recipient attempt
- Accepted attemptIdempotent blast_sent contact activity
- 1
Compare the recorded sent count
Recent blasts > Sent row > Audience
Compare the recorded sent count with the effective audience recorded during preflight, using the displayed summary as context.
Expected result: A lower recorded sent count and broker-safe reason identify a partial result without exposing the affected addresses.
If this does not happen: A manual reconciliation can include previously unresolved rows in the recorded sent count. Do not resend or guess which addresses failed. Contact support with the exact operation evidence.
- 2
Verify CRM timeline evidence
CRM > Contacts > Person > Timeline
For a known recipient, look for blast_sent only after terminal campaign acceptance and an accepted recipient attempt.
Expected result: The timeline reflects accepted hosted campaign activity once, not a composer click.
If this does not happen: A missing timeline event does not justify resending. Check campaign status and recipient outcome first.
- 3
Handle a Downloaded row
Recent blasts > Downloaded
Confirm that the event represents file generation only.
Expected result: No CREBuilder-hosted recipient is treated as sent.
If this does not happen: Complete and verify the send in the chosen external platform. CREBuilder cannot report that platform’s outcome from this row.
Recipient-level and support evidence stay private
A reviewed hosted Sent row retains the accepted count, durable suppression total, and a broker-safe partial or reconciliation summary. It does not expose failed recipient identities, the reviewer identity, or pasted provider evidence. Support keeps that operator evidence in the restricted audit record. Preserve the subject, sender, timestamp, preflight audience count, and operation identifier if shown.
Report only what history proves
| Question | What Recent blasts can prove |
|---|---|
| Was hosted transport accepted? | Sent or a more specific durable recipient result can support accepted-attempt language. |
| Was the message delivered to the inbox? | No. Provider acceptance is not inbox placement. |
| Did the person open or click? | No. Open/click analytics are not exposed. |
| Was a future send scheduled? | No. Hosted scheduling is not available. |
| Was downloaded HTML sent externally? | No. Downloaded proves file generation only. |
| Which recipients failed in a reviewed Sent campaign? | The row retains a broker-safe partial summary, not a failed-recipient list. Use support rather than guessing or resending. |
| Is this the full company archive? | No. The hub shows the latest 50 returned rows. |
A campaign is no longer in the visible table
Likely cause: More than 50 newer history rows exist.
- Do not describe the hub as full history.
- Collect subject, approximate date, sender, method, and recipient context.
- Use the documented support path for older evidence.
A row remains Sending or Outcome unconfirmed
Likely cause: The durable reconciliation process has not established a terminal transport result.
- Do not resend.
- Refresh after a reasonable interval.
- Preserve screenshots and operation context.
- Contact support if it does not settle.
A recipient says the message was not received although status is Sent
Likely cause: Accepted transport does not guarantee inbox placement.
- Confirm the exact address.
- Ask the recipient to check filtering or quarantine.
- Review later bounce or complaint suppression state.
- Do not claim open or delivery telemetry that the product does not expose.
Final verification
- Recent blasts > status and detail: The next action follows the evidence that the row actually exposes.
- Recent blasts > Sent row > Audience: A lower recorded sent count and broker-safe reason identify a partial result without exposing the affected addresses.
- CRM > Contacts > Person > Timeline: The timeline reflects accepted hosted campaign activity once, not a composer click.
- Recent blasts > Downloaded: No CREBuilder-hosted recipient is treated as sent.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.