Understand provider request limits and errors
Interpret controlled HTTP failures.
Exact navigationAdmin Area → Courier & Logistics → Settings → Providers → Test / Sync Logs
What this guide covers
Interpret controlled HTTP failures. 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
- Open Admin Area → Courier & Logistics → Settings → Providers → Test / Sync Logs.
- Review the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
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
- Requests use public HTTPS validation and TLS controls.
- Responses are capped at 5 MB.
- Structured errors retain message, HTTP status and sanitised data/raw excerpt.
- OAuth token acquisition is separate from the final provider request.
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.