Refresh a live provider feed

Force a provider fetch when the cache is stale or an authorised refresh is needed. 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

Force a provider fetch when the cache is stale or an authorised refresh is needed. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Select the provider.
2. Use Refresh/force sync.
3. Check response and sync log.
4. Check normalised jobs in the cache.

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

• Normal cache use respects provider interval and a minimum live-cache age.
• Courier Exchange detail calls are throttled and normalisation is capped at 500 jobs.

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