Verify cron after deployment | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/verify-cron-after-deployment Publisher: Pixie Technologies LLC Settings, cron automation and technical code flow Verify cron after deployment Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Prove scheduled automation runs without duplicating work. Audience: Courier operations staff; Permission: Courier: Administrator; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Settings / Logs What this guide helps you do Prove scheduled automation runs without duplicating work. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Run the supported cron once manually. - Check module sync/audit/notification records. - Run it again. - Verify due checks prevent duplicate reports and excessive provider calls. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - Use the supported screen and permission; do not bypass validation or edit database records directly. Check it worked - The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action. Security, audit and operational checks - Use the exact record and least-privilege role before changing any state. - Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed. - Use protected document and image routes rather than exposing server filesystem paths. - Keep customer, driver, provider, financial and credential data within the authorised workflow. - For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process. Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful. Related guides Configure general Courier settings (https://pixiecrm.com/help-centre/configure-general-courier-settings)Run Courier cron automation (https://pixiecrm.com/help-centre/run-courier-cron-automation)Understand the Courier automation sequence (https://pixiecrm.com/help-centre/understand-the-courier-automation-sequence)Understand core CRM hooks used by Courier (https://pixiecrm.com/help-centre/understand-core-crm-hooks-used-by-courier)