Understand oldest queued campaign selection | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-oldest-queued-campaign-selection Publisher: Pixie Technologies LLC Queue, rate limit and cron Understand oldest queued campaign selection Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains that which campaign autonomous processing chooses when no campaign ID is requested. Audience: Administrators and developers; Permission: Staff login; Module v1.0.0; Where to goAutomatic queue control → CRM cron 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 Know which campaign autonomous processing chooses when no campaign ID is requested. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Allow cron to invoke the queue without a requested campaign. - Check Newsletter History after the run. - Verify the oldest queued or sending campaign with pending recipients progressed first. Fields and options Action scopeKnow which campaign autonomous processing chooses when no campaign ID is requested. Module version1.0.0 NavigationAutomatic queue control → CRM cron 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)Close the newsletter page safely (https://pixiecrm.com/help-centre/close-the-newsletter-page-safely)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)