Understand Letter Manager email automation limitations
Follow this guide to use manual send/resend without assuming a queue, retry scheduler or cron exists. 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.
Where to goAdmin Area → Letter Manager → Dashboard / Sent Letters History
Before you start
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What you’ll accomplish
Use manual send/resend without assuming a queue, retry scheduler or cron exists. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Send letters from the dashboard.
- Use Resend Email manually after correcting a failure.
- Monitor status and logs.
- Use an approved external process only if the organisation needs queued retries or scheduled dispatch.
Fields and options to review
Action scopeUse manual send/resend without assuming a queue, retry scheduler or cron exists.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard / Sent Letters History
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- The module registers no cron hook.
- No email queue table or scheduled-send field is implemented.
- No automatic failure retry or delivery-bounce processing is included.
How to confirm it worked
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.