Continue newsletter delivery through cron
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use the module after_cron_run hook so queued campaigns progress after the browser closes.
Where to goAdmin Area → Setup → Cron Job, then Admin Area → Letter Manager → Email Marketing / Newsletter → History
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 this guide helps you do
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.
Follow these steps
- Check 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.
- Verify Sent, Failed and Remaining changed.
Fields and options
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
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- The autonomous cron processor requests up to 100 attempts per run.
- The same rolling five-minute allowance is shared with browser processing.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.