Understand the 100 emails per five minutes limit

Apply the exact global rolling-window rule enforced by the queue. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

Apply the exact global rolling-window rule enforced by the queue. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

1. Start or continue a campaign normally.
2. When rate-limited, wait for the oldest counted attempt to leave the 300-second window.
3. Allow the page or cron to retry.

Fields and options to review

Rules the system enforces

• The queue counts processing, sent and failed recipients with attempted_at in the preceding 300 seconds.
• Allowance equals 100 minus the number already counted across campaigns.
• The minimum returned wait is five seconds; a fallback wait of 60 seconds is used when required.

How to confirm it worked

• The requested record, output or setting is created or updated through the supported module flow.
• Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
• An error message is investigated rather than bypassed.

Security, privacy and operational checks

• Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
• Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
• Test configuration changes with controlled records before production-wide use.
• Retain or delete evidence only under an authorised retention process.

Continue with related guidance