Understand provider live-job caching

Follow this guide to use cache and force refresh without excessive provider calls. 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

Use cache and force refresh without excessive provider calls. 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 Admin Area → Courier & Logistics → Live Jobs.
2. Check the source record and choose the supported action.
3. Save or submit once, then reopen the record and verify the result.

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

• Provider cache is scoped by provider.
• A minimum 15-second cache age limits repeated live calls.
• Configured polling intervals control normal refresh.
• Courier Exchange detail loads are handled one at a time with stale-data controls.

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.

Continue with related guidance