Troubleshoot Delivery Note email delivery
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Check creation/signing conditions and the global mail dependency without altering note evidence.
Where to goAdmin Area → Delivery Note → Open note, then Admin Area → Setup → Settings → Email
What this guide helps you do
Check creation/signing conditions and the global mail dependency without altering note evidence. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Verify Recipient Email is present and correctly formatted.
- Identify whether the missing message is dispatch or signed confirmation.
- Verify the corresponding note creation or signed status actually completed.
- Test the global CRM email configuration.
- Check SMTP host, port, sender, encryption and decrypted-password behaviour.
- Check application/email logs and recipient spam/quarantine.
- Use the existing secure link manually if operationally authorised.
Fields and options
- Recipient email
- Reference and status
- Global email protocol and SMTP options
- Application mail logs
Rules and limits
- There is no built-in resend action.
- There is no module event confirming send success or failure.
- A blank email intentionally suppresses both automated messages.
- Do not modify the stored signature or status to trigger another email.
Check it worked
- The mail issue is identified while the delivery note and event evidence remain unchanged.
Safety checks and troubleshooting
- Any manual re-send should use an approved communication process and protect the bearer link.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Related guides
Was this guide useful?Your response is stored only in this browser.