Continue newsletter delivery through cron
Use the module after_cron_run hook so queued campaigns progress after the browser closes.
Exact navigationAdmin Area → Setup → Cron Job, then Admin Area → Letter Manager → Email Marketing / Newsletter → History
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
Use the module after_cron_run hook so queued campaigns progress after the browser closes. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Verify the normal CRM cron runs successfully.
- Start a campaign.
- Close or leave the newsletter page if required.
- After the next cron runs, reopen Newsletter History.
- Confirm Sent, Failed and Remaining changed.
Fields, choices and supported possibilities
Action scopeUse the module after_cron_run hook so queued campaigns progress after the browser closes.
Module version1.0.0
NavigationAdmin Area → Setup → Cron Job, then Admin Area → Letter Manager → Email Marketing / Newsletter → History
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The autonomous cron processor requests up to 100 attempts per run.
- The same rolling five-minute allowance is shared with browser processing.
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.