Understand newsletter queue locking
Prevent browser and cron workers from processing the same queue simultaneously. 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.
Where to goAutomatic queue control → MySQL campaign queue lock
Before you start
- 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 you’ll accomplish
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.
Follow these steps
- Allow normal browser and cron processing to run.
- If a worker reports busy, do not start a second manual process.
- Wait at least the returned five-second busy interval and retry.
Fields and options to review
Action scopePrevent browser and cron workers from processing the same queue simultaneously.
Module version1.0.0
NavigationAutomatic queue control → MySQL campaign queue lock
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- 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.
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
Was this guide useful?Your response is stored only in this browser.