Self-hosted Chatwoot v4.18.0 WhatsApp campaign shows Completed but no message is delivered #16284
Unanswered
PradyumnaDevulapally
asked this question in
Self hosted
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi Chatwoot team,
I'm running a self-hosted Chatwoot instance and need help troubleshooting WhatsApp campaigns. I can now create and schedule campaigns, but no WhatsApp message is received by the test contact, even though the campaign status changes to Completed.
Environment
Chatwoot version: 4.18.0
Deployment: Self-hosted on AWS EC2 using Docker Compose
Edition: Community Edition (self-hosted)
WhatsApp integration: WhatsApp Cloud API
Inbox used: Sales
What I did
Enabled the whatsapp_campaign account feature flag through the Super Admin account settings. The WhatsApp Campaign option then appeared in the sidebar.
Created a dedicated label named test_campaign_cohort.
Assigned the label to the intended test contact.
Created a WhatsApp campaign titled TEST - WhatsApp Campaign - Internal.
Selected the Sales WhatsApp inbox.
Selected an existing Meta-approved WhatsApp template (Welcome Message New (en)).
Selected test_campaign_cohort as the audience.
Scheduled the campaign for a future time.
Observed behaviour
The campaign was initially marked Scheduled.
After the scheduled time passed, it eventually changed to Completed.
However, no WhatsApp message was received by the test contact.
I created a second test campaign with another approved template, but the same behaviour occurred.
Campaign analytics are unavailable in my Community Edition installation, so I cannot inspect recipient or delivery statistics through the UI.
Checks already performed
Confirmed that the running Rails container uses chatwoot/chatwoot:v4.18.0.
Confirmed that Super Admin → Instance Status reports version 4.18.0 and database migrations as completed.
Confirmed that both WhatsApp inboxes use the whatsapp_cloud provider.
Confirmed that the local application and public HTTPS endpoint return HTTP 200.
Confirmed that Nginx proxies the public domain to the local Rails service.
Checked Sidekiq logs for the terms campaign, whatsapp, error, exception, and failed; no matching log lines were returned.
Questions
Does Completed mean only that the campaign job finished processing, or does it confirm that messages were successfully submitted to Meta?
Is there a known issue in Chatwoot v4.18.0 where scheduled WhatsApp campaigns transition to Completed without sending messages?
How can I verify the number of recipients selected and whether Chatwoot attempted to send a message to each recipient without Enterprise campaign analytics?
Which Rails or Sidekiq logs, jobs, or database records should I inspect to determine whether the campaign was processed and whether Meta accepted or rejected the messages?
Are there any additional requirements for WhatsApp Cloud API campaigns on a self-hosted Community Edition installation beyond enabling the account feature flag, using a WhatsApp Cloud API inbox, selecting a label-based audience, and choosing an approved template?
I only need one-time WhatsApp template broadcasts; I do not require campaign analytics or WhatsApp Calling.
Thank you for your help.
All reactions