Refresh a live provider feed | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/refresh-a-live-provider-feed Publisher: Pixie Technologies LLC Provider live jobs and external imports Refresh a live provider feed Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Force a provider fetch when the cache is stale or an authorised refresh is needed. Audience: Courier operations staff; Permission: Courier: Manage integrations; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Live Jobs → Refresh What this guide helps you do 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 - Select the provider. - Use Refresh/force sync. - Check response and sync log. - Check normalised jobs in the cache. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - 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. Check 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. 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. Related guides Open Live Jobs for a provider (https://pixiecrm.com/help-centre/open-live-jobs-for-a-provider)Import an external job (https://pixiecrm.com/help-centre/import-an-external-job)Understand provider-job normalisation (https://pixiecrm.com/help-centre/understand-provider-job-normalisation)Prevent duplicate external imports (https://pixiecrm.com/help-centre/prevent-duplicate-external-imports)