Understand automated vehicle-expiry enforcement | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-automated-vehicle-expiry-enforcement Publisher: Pixie Technologies LLC Compliance workspaces and alerts Understand automated vehicle-expiry enforcement 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 what the cron automation changes when monitored dates pass. Audience: Courier operations staff; Permission: Courier: Manage compliance; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Compliance What this guide helps you do Know what the cron automation changes when monitored dates pass. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Check the vehicle before the due date. - Allow scheduled automation to run. - If a date is past, verify compliance becomes expired and availability unavailable. - Renew evidence and update the record before restoring availability. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - Automation checks monitored expiry fields. - It does not validate the underlying document’s legal adequacy. 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 Open Courier compliance alerts (https://pixiecrm.com/help-centre/open-courier-compliance-alerts)Review driver compliance alerts (https://pixiecrm.com/help-centre/review-driver-compliance-alerts)Review vehicle compliance alerts (https://pixiecrm.com/help-centre/review-vehicle-compliance-alerts)Understand compliant, pending, action-required and expired states (https://pixiecrm.com/help-centre/understand-compliant-pending-action-required-and-expired-states)