Recover stale processing recipients
Understand the automatic recovery of rows left in processing by an interrupted worker.
Exact navigationAutomatic queue control → Next browser or cron queue run
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
Understand the automatic recovery of rows left in processing by an interrupted worker. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Allow the next queue run to start.
- Open campaign Details after processing.
- Verify recipients left processing for more than 15 minutes return to pending and can be attempted again.
Fields, choices and supported possibilities
Action scopeUnderstand the automatic recovery of rows left in processing by an interrupted worker.
Module version1.0.0
NavigationAutomatic queue control → Next browser or cron queue run
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- Recovery stores an explanatory error on the reset recipient row.
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.