Troubleshoot a provider connection failure

Resolve URL, auth, endpoint, mapping or network validation. 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.

What you’ll accomplish

Resolve URL, auth, endpoint, mapping or network validation. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Check sanitised error and HTTP status.
2. Verify public HTTPS URL.
3. Verify auth method and credentials.
4. Verify endpoint path.
5. Validate mapping JSON.
6. Retest.

Fields and options to review

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules the system enforces

• Use the supported screen and permission; do not bypass validation or edit database records directly.

How to confirm it worked

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Errors and rejected actions

• Private/non-HTTPS destination rejected.
• OAuth token failure.
• Invalid credentials or endpoint.
• Response larger than 5 MB.
• Invalid JSON mapping.

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.

Continue with related guidance