Queue, rate limit and cron

Process a newsletter in the browser

Allow the campaign page to request immediate queue work in small chunks. 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.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → Active campaign progress
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

Allow the campaign page to request immediate queue work in small chunks. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Start the campaign.
  2. Keep the newsletter tab open.
  3. Watch Sent, Failed and Remaining counters.
  4. Allow the page to continue its process polling until completed or rate-limited.

Fields and options to review

Action scopeAllow the campaign page to request immediate queue work in small chunks.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Active campaign progress
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The browser endpoint asks the queue for up to 20 recipient attempts per request.
  • Browser polling does not override the global 100-attempt rolling limit.

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.