Queue, rate limit and cron

Understand the 100 emails per five minutes limit

Apply the exact global rolling-window rule enforced by the queue.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAutomatic queue control → Browser processing and CRM cron
Before you begin
  • Use an authorised account and confirm the source CRM record or setting is correct.
  • Follow the exact route shown above; do not force database values to imitate a completed action.

What this guide covers

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.

Exact step-by-step process

  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, choices and supported possibilities

Action scopeApply the exact global rolling-window rule enforced by the queue.
Module version1.0.0
NavigationAutomatic queue control → Browser processing and CRM cron
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • 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.