- The affected campaign, channel, and approximate send time
- Recipient-level status for one redacted failed example
- Current sender, audience, consent, and suppression evidence
- Authority to pause or recover the campaign without duplicating delivery
Start in the Campaign center
Open Campaigns and filter by channel and status: Draft, Scheduled, Sending, Sent, Failed, or Cancelled. “Sent with issues” can mean the campaign completed while some recipients were skipped or failed; it is not the same as a campaign that never started.
Campaign recovery position
- 01AudienceGoverned audience
Eligible contacts, consent, and suppressions define who may receive it.
- 02ContentApproved content
Channel, sender, variables, links, and claims are ready.
- 03ControlTest and review
A representative test proves rendering and recipient context.
- 04LaunchSchedule or send
An authorized person commits the final audience and time.
- 05LearnDelivery and responder follow-up
Exceptions and replies become owned operational work.
Diagnose the scope
- Open the campaign detail.
- Record channel, sender, template/content, schedule, audience snapshot, and campaign status.
- Inspect the recipient log and filter Failed or skipped recipients.
- Read row-level status, timestamps, skip reason, and provider error.
- Open Settings → Message delivery and check whether the problem affects the same sender or many campaigns.
- Fix the underlying cause before using any retry control.
| Pattern | Likely cause | Response |
|---|---|---|
| No sendable recipients | Consent, suppression, invalid address/number, or audience snapshot | Review excluded/skipped reasons; do not override compliance |
| WhatsApp template missing | Wrong sender library, unsynced, rejected, or unavailable template | Select connected sender and sync an approved template |
| Many failures on one sender | Provider or connection health | Pause new sends; diagnose channel settings |
| One/few recipient failures | Recipient or provider-specific error | Correct eligible data, then retry failed only when available |
| Scheduled at wrong time | Schedule configuration | Use Edit schedule; audience and recipient snapshot stay unchanged |
| Campaign remains Sending | Processing has not reached a final state | Do not start a duplicate; preserve campaign status and timestamps, then contact WRKZY Support |
WhatsApp failed-recipient retry
When the detail page offers Retry failed, review the count and confirmation. The action retries only failed recipients; successful recipients will not be resent. A running retry job blocks another retry. After confirming, watch the recipient log and Message delivery.
Do not use retry for suppressed, frequency-guardrail, unconsented, or already-successful recipients.
Scheduled campaigns
Edit schedule changes only the scheduled time while keeping audience and recipient snapshot. Cancel schedule returns a WhatsApp campaign to draft and removes its recipient snapshot according to the confirmation. Re-review audience before scheduling again.
Email campaign scheduling has its own channel-specific controls; use the email campaign detail and do not assume WhatsApp recovery actions apply identically.
Recovery and escalation
For broad risk, pause dependent automations and hold new campaigns. Preserve campaign ID, channel, job ID/status, sender/connection ID, template ID/status, audience snapshot count, failed/skipped counts, one redacted provider reason, schedule/timezone, and actions tried. Never include provider credentials or an unsanitized recipient export.
- Campaign and recipient states distinguished
- Sender/template health checked
- Consent and suppression preserved
- Only eligible failed recipients retried
- Schedule semantics understood
- Recipient log reached expected outcomes