Open Delivery and Queue Health first. What you see there tells you which cause applies.
The rows say Failed with an error
Read the Error Detail column. MsgOrb translates Meta's codes into plain language. Match it below.
No template is approved
Symptom: *Template "X" is not approved on WhatsApp yet.*
Meta requires an approved template for every message you start. Open Templates, click Submit to Meta on the template, wait, then click Sync Status. See Submitting a template to Meta.
The 24-hour window is closed
Symptom: *Outside the 24-hour reply window* (Meta 131047).
You sent free-form to someone who has not messaged you in the last 24 hours. Use an approved template, or ask the recipient to message you first. See The 24-hour window.
The token expired or lacks permissions
Symptom: a red banner across the dashboard, or *Your WhatsApp access token does not have the permissions Meta requires* (Meta 131005).
Generate a permanent System User token with both whatsapp_business_messaging and whatsapp_business_management. See Access tokens and permissions.
Meta withheld the message
Symptom: *Meta withheld this message* (Meta 131049).
Almost always the template has been categorised MARKETING. Meta blocks marketing templates to United States (+1) numbers. Check the category on Templates. See Template rejected or reclassified.
You are on a Meta test number
Symptom: *Recipient is not in your Meta test allowlist* (Meta 131030).
A test number only delivers to a few allowlisted recipients. Add the number in Meta Dashboard → WhatsApp → API Setup, or move to your own verified number.
The recipient cannot receive WhatsApp
Symptom: *This number cannot receive WhatsApp messages* (Meta 131026).
The number has no WhatsApp account, or was typed wrongly. Correct it in the roster.
The rows say Pending and never move
The dispatcher is not running. It normally runs every five minutes, and MsgOrb also kicks it right after you queue a send. If Queue Latency on the Dashboard keeps climbing while nothing moves, this is a deployment-level problem rather than a configuration one — contact support at support@msgorb.com with the approximate time the queue stalled.
There are no rows at all
The workflow never queued anything. Check that the target group has active members: contacts that are pending, opted out or bounced are skipped. The builder refuses outright with *"X" has no active members to send to*.