Troubleshoot a dispatch rejection

Resolve the exact failed eligibility rule. 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 the exact failed eligibility rule. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Go to the job, driver and vehicle separately.
2. Check job status/unassigned state, receiver name/email and agreed revenue.
3. Check driver employment, availability, compliance and email.
4. Check vehicle availability and compliance.
5. Correct the source record and retry.

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

• Invalid job status or existing assignment.
• Missing receiver or invalid receiver email.
• Agreed revenue is zero/not positive.
• Driver inactive, unavailable, non-compliant or invalid email.
• Vehicle inactive, unavailable or non-compliant.

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