Troubleshooting and verified limitations

Troubleshoot a stuck newsletter campaign

Separate cron, queue-lock, rate-limit, stale-processing and SMTP causes.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAdmin 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

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.

Exact step-by-step process

  1. Confirm Remaining is greater than zero.
  2. Run and verify the normal CRM cron.
  3. Wait for any rolling rate window.
  4. Allow stale processing rows more than 15 minutes old to be recovered.
  5. Review failed recipient errors and server logs.

Fields, choices and supported possibilities

Action scopeSeparate cron, queue-lock, rate-limit, stale-processing and SMTP causes.
Module version1.0.0
NavigationAdmin 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

  • 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.

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.