Sending and Throttling
Sending is deliberately gradual. A campaign is claimed in batches by a background task rather than dispatched at once.
Where to find it
Architect Panel → Commercial:
- Campaign Manager — schedule, monitor, pause
Architect Panel → Automation:
- Tasks — E-mail Campaign Sender, every 5 minutes
Architect Panel → Activity:
- E-mail Log — each message and its result
Throttling
The messages per minute setting caps the rate. It is not a performance limitation — it is a deliverability control.
Sending ten thousand e-mails in a minute from a domain that normally sends fifty a day is the single clearest signal of a compromised account, and receiving mail systems treat it accordingly. The result is your messages in spam folders, and a sending reputation that takes weeks to repair.
Spreading the same campaign over an hour or two looks like normal traffic and lands in inboxes.
Choosing a rate
Be conservative on a domain with no bulk-sending history. Start low, watch the results, and increase over subsequent campaigns as your reputation establishes.
If a campaign genuinely must arrive within a narrow window, that is a reason to plan it earlier, not to remove the throttle.
Scheduling
A campaign set to a future time waits at Scheduled until the sender task picks it up. Since the task runs every five minutes, sending starts within that window rather than exactly on the second — fine for marketing, worth knowing if timing matters.
Pausing
A campaign in flight can be paused. Nothing further is claimed, and what has already gone has gone.
Know how to do this before you need it. The moment you need it — a wrong link, a wrong name, a wrong audience — is not the moment to be learning where the control is. Every minute of hesitation is more messages sent.
What to do after pausing
Establish how many were sent and to whom before doing anything else; the recipient records tell you exactly. Then decide whether to fix and resume, cancel, or follow up with a correction — and remember that a correction e-mail to people who received the original is itself a send that needs care.
Reading the outcome
Each recipient carries its own status, send time, a link to the message in the e-mail or SMS log, and any error. So a campaign that reports partial success can be broken down into exactly who did not receive it and why.
Look at the failures on every campaign, not just problematic ones. A rising bounce rate is the earliest sign your data is decaying.
Do not resend to everybody
When something goes wrong, the instinct is to resend the campaign. Send to the people who did not receive it, not to the whole segment — receiving the same message twice is the most reliable way to generate unsubscribes.
Worked example
A charity schedules an appeal to 12,000 supporters at 40 per minute, so it sends over five hours starting at 07:00. Twenty minutes in, someone spots the donation link points at the test site. The campaign is paused with about 800 sent; the link is fixed, those 800 are sent a brief correction, and the remainder go out on the corrected campaign.
Recommendations
- Always throttle — start conservative and build up.
- Find the pause control before your first real campaign.
- Review failures after every send.
- Never resend to the whole segment.