Handle an expired POD link
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to create a controlled replacement or update through the supported process.
Where to goAdmin Area → Courier & Logistics → Delivery Notes → Open note
What this guide helps you do
Create a controlled replacement or update through the supported process. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Verify the token is expired.
- Do not reuse the expired public URL.
- Use the supported note/job action to issue a valid request.
- Send the new/current link to the authorised recipient.
Fields and options
This action uses the values already stored on the selected source record. Review that record before continuing.
Rules and limits
- Public signing rejects expired tokens.
- Expiry is set for at least one day at creation.
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
Was this guide useful?Your response is stored only in this browser.