Queue, rate limit and cron

Understand newsletter queue locking

Prevent browser and cron workers from processing the same queue simultaneously.

Audience: Administrators and developersPermission: Staff loginModule v1.0.0
Exact navigationAutomatic queue control → MySQL campaign queue lock
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

Prevent browser and cron workers from processing the same queue simultaneously. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Allow normal browser and cron processing to run.
  2. If a worker reports busy, do not start a second manual process.
  3. Wait at least the returned five-second busy interval and retry.

Fields, choices and supported possibilities

Action scopePrevent browser and cron workers from processing the same queue simultaneously.
Module version1.0.0
NavigationAutomatic queue control → MySQL campaign queue lock
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • The queue uses MySQL GET_LOCK with a database-prefix-specific lock name capped at 64 characters.
  • A worker that cannot acquire the lock returns success with busy/rate_limited metadata rather than duplicating sends.

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.