Understand the Courier automation sequence
This guide explains that the major tasks run by the model automation entry point. 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.
Where to goServer scheduler → after_cron_run → Courier run_automation
What you’ll accomplish
Know the major tasks run by the model automation entry point. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to Server scheduler → after_cron_run → Courier run_automation.
- Check the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields and options to review
ComplianceRecalculate/check driver and vehicle conditions and enforce vehicle expiry.
ProvidersPoll active integrations when due.
BP fuelFetch transactions when active and due.
POD/providerContinue eligible staged submissions/retries.
Daily digestSend due operational/driver summaries once per date.
Rules the system enforces
- Each sub-workflow retains its own last-run/sync evidence and eligibility checks.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.