Troubleshoot missing newsletter recipients
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Resolve active-status, invalid-email, grouping or stale-directory causes.
Where to goAdmin Area → Customers / Leads, then Letter Manager → Email Marketing / Newsletter
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
Resolve active-status, invalid-email, grouping or stale-directory causes. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to the missing contact or lead in the CRM.
- Verify the contact is active where applicable.
- Enter a valid email.
- Verify customer-group or lead-status membership for group selection.
- Reload the newsletter tab.
Fields and options
Action scopeResolve active-status, invalid-email, grouping or stale-directory causes.
Module version1.0.0
NavigationAdmin Area → Customers / Leads, then Letter Manager → Email Marketing / Newsletter
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
Was this guide useful?Your response is stored only in this browser.