Queue, rate limit and cron

Recover stale processing recipients

This guide explains the automatic recovery of rows left in processing by an interrupted worker. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAutomatic queue control → Next browser or cron queue run
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 you’ll accomplish

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.

Follow these steps

  1. Allow the next queue run to start.
  2. Go to campaign Details after processing.
  3. Check recipients left processing for more than 15 minutes return to pending and can be attempted again.

Fields and options to review

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
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Recovery stores an explanatory error on the reset recipient row.

How to confirm 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.