A campaign is stuck, paused or won't start
A campaign that will not start usually has no connected device, no recipients, or no messages. A scheduled campaign that never fired usually means BuzzRelay was closed or the computer was asleep at that moment — there is no cloud component, so the app has to be running. A campaign that looks frozen is often just waiting out a long delay between recipients.
It will not start at all
| Check | Requirement |
|---|---|
| Device | A device must be assigned and showing connected. |
| Messages | At least one message is required. |
| Recipients | At least one contact or group must be selected. |
| Daily limit | If the device already hit its limit today, there is nothing left to send. |
| Quiet Hours | If enabled and you are inside the blocked window, sending waits. |
The device is the usual one. A device that was connected yesterday may have dropped its session overnight — open Devices and confirm green before starting.
A scheduled campaign never ran
BuzzRelay has to be running at the scheduled time. There is no cloud component and nothing runs server-side. If the app was closed, the PC was off, or Windows had gone to sleep, the campaign simply did not fire.
Things to check:
- Was BuzzRelay open? Scheduling does not launch the app.
- Did the PC sleep? Check Windows power settings — a machine that sleeps after 30 minutes will miss an overnight schedule and interrupt a long campaign.
- Was the device connected? A disconnected device cannot send when the time comes.
- Were you inside Quiet Hours? A schedule inside the blocked window will not send.
If campaigns need to run while you are away, a Windows VPS that stays on is the usual answer — see System requirements.
It looks frozen
Usually it is not. Check the delay settings before assuming something is wrong:
| Delay range | Gap between recipients |
|---|---|
| 5–15 seconds | Up to 15 seconds of apparent inactivity |
| 30–90 seconds | Up to a minute and a half |
| 60–120 seconds | Up to two minutes |
With wide delays, a campaign genuinely looks idle most of the time. Watch the sent count over a few minutes rather than a few seconds.
If nothing has moved for much longer than your maximum delay:
- Check the device is still connected — a dropped session stops progress.
- Check the phone is online.
- Check whether the daily limit was reached — remaining recipients are marked skipped and the campaign completes.
- Look at
%APPDATA%\BuzzRelay\logs\app.logfor the last recorded action.
It paused itself
A campaign stops rather than pushing on when something is wrong — most often the device disconnecting mid-run. Recipients not yet reached stay pending.
Reconnect the device and resume. Do not create a new campaign for the remainder, or everyone already messaged receives it a second time — see Campaign and recipient statuses.
It completed far too quickly
A campaign that finishes in seconds has not really sent. Look at the recipient statuses:
- All failed — the device was not genuinely connected, or every number was malformed. See Messages are failing to send.
- All skipped — the daily limit was already used up today.
- Fewer recipients than expected — the group had fewer contacts than you thought, or contacts overlapped and were de-duplicated.
Restarting cleanly
If a campaign is in a state you cannot resolve, close BuzzRelay completely, end any lingering BuzzRelay.exe in Task Manager, and reopen. Recipient statuses are stored as it goes, so nothing already sent is lost and resuming will not re-send to them.
Frequently asked questions
Why did my scheduled WhatsApp campaign not send?
BuzzRelay must be running at the scheduled time — there is no cloud component. The usual causes are the app being closed, the computer being asleep or off, the device having disconnected, or the schedule falling inside your Quiet Hours window.
My campaign looks frozen. Is it broken?
Usually not. With a 30 to 90 second delay range, a campaign is idle for up to a minute and a half between recipients. Watch the sent count over several minutes. If nothing moves for much longer than your maximum delay, check the device is still connected.
Why will my campaign not start?
It needs an assigned device that is currently connected, at least one message, and at least one recipient. A device that was connected yesterday may have dropped its session overnight, so check for a green status first.
My campaign completed in seconds. What happened?
It did not really send. Check the recipient statuses: all failed usually means the device was not genuinely connected or the numbers were malformed, and all skipped means the device had already reached its daily limit today.
Last updated: