Troubleshoot a stuck newsletter campaign | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/troubleshoot-a-stuck-newsletter-campaign Publisher: Pixie Technologies LLC Troubleshooting and verified limitations Troubleshoot a stuck newsletter campaign Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Separate cron, queue-lock, rate-limit, stale-processing and SMTP causes. Audience: CRM staff; Permission: Staff login; Module v1.0.0; Where to goAdmin 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 Separate cron, queue-lock, rate-limit, stale-processing and SMTP causes. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Verify Remaining is greater than zero. - Run and verify the normal CRM cron. - Wait for any rolling rate window. - Allow stale processing rows more than 15 minutes old to be recovered. - Check failed recipient errors and server logs. Fields and options Action scopeSeparate cron, queue-lock, rate-limit, stale-processing and SMTP causes. Module version1.0.0 NavigationAdmin 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 - Only values and transitions exposed by the supplied module code are supported. - Server-side validation remains authoritative even when browser controls appear to accept a value. 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 Email Marketing & Newsletter module overview (https://pixiecrm.com/help-centre/email-marketing-newsletter-module-overview)Troubleshoot a rate-limited newsletter (https://pixiecrm.com/help-centre/troubleshoot-a-rate-limited-newsletter)Troubleshoot missing predefined newsletter templates (https://pixiecrm.com/help-centre/troubleshoot-missing-predefined-newsletter-templates)Understand Email Marketing & Newsletter limitations (https://pixiecrm.com/help-centre/understand-email-marketing-newsletter-limitations)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)