Review provider sync logs
Use timing, request type and sanitised response evidence for troubleshooting.
Exact navigationAdmin Area → Courier & Logistics → Settings → Providers → Sync Logs
What this guide covers
Use timing, request type and sanitised response evidence for troubleshooting. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Filter by provider and sync type.
- Review start/end, success, HTTP status and processed count.
- Open affected jobs/invoices/POD records.
- Correct configuration and rerun only the failed action.
Fields, choices and supported possibilities
This action uses the values already stored on the selected source record. Review that record before continuing.
Code-backed validations and workflow rules
- Secrets are redacted.
- The log complements the operational record and provider evidence.
Expected result and verification
- 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.