Notifications, email logs and cron automation
Understand all event recipients, deduplication, retries, due/overdue reminders and SMTP behaviour.
Service Journeys
Open guide →GuideUnderstand Service Journeys notifications
The notification library writes deduplicated log rows and attempts immediate email where recipients apply.
Open guide →GuideUnderstand staff recipients
Assigned staff are used first; otherwise active administrators receive staff notifications.
Open guide →GuideUnderstand client recipients
A linked active contact is preferred; otherwise the stored contact email is used.
Open guide →GuideUnderstand activity notification rule
Client email is considered only when the activity is marked visible; no staff email is generated for staff-added activity.
Open guide →GuideUnderstand task notification rule
Clients are notified when a task is visible or client action is required.
Open guide →GuideUnderstand task-completion notification rule
Clients are notified only when the completed task is visible.
Open guide →GuideUnderstand message direction
Staff messages notify client; client messages notify staff.
Open guide →GuideUnderstand document notification direction
Visible staff documents notify client; client documents notify staff.
Open guide →GuideUnderstand due/overdue recipients
Due and overdue reminders are staff-only.
Open guide →GuideUnderstand notification deduplication
A hash prevents the same event/recipient payload being queued repeatedly.
Open guide →GuideUnderstand immediate email attempts
New log rows are attempted immediately.
Open guide →GuideUnderstand failed email status
Failed attempts retain error evidence for retry.
Open guide →GuideUnderstand retry limit
Failed notifications are retried no more than three attempts.
Open guide →GuideUnderstand first retry timing
The first failed attempt becomes eligible after 15 minutes.
Open guide →GuideUnderstand second retry timing
The second failed attempt becomes eligible after 60 minutes.
Open guide →GuideUnderstand cron retry batch
Each cron run retries at most 25 eligible failed notifications.
Open guide →GuideUnderstand due-soon reminders
Outstanding applications due within three days are eligible.
Open guide →GuideUnderstand overdue reminders
Outstanding applications with a due date before today are eligible.
Open guide →GuideUnderstand reminder scan size
Due/overdue processing evaluates up to 250 application rows.
Open guide →GuideRun notification automation
The module hooks before_cron_run and calls the notification processor.
Open guide →GuideUnderstand sender address selection
The library checks smtp_email, company_email and companyemail options.
Open guide →GuideUnderstand BCC configuration
Configured bcc_emails can be applied.
Open guide →GuideReview notification evidence
Inspect pending, sent, failed or skipped log entries and errors.
Open guide →GuideUnderstand event: Application created
The notification/audit layer recognises the Application created event.
Open guide →GuideUnderstand event: Status changed
The notification/audit layer recognises the Status changed event.
Open guide →GuideUnderstand event: Case updated
The notification/audit layer recognises the Case updated event.
Open guide →GuideUnderstand event: Activity added
The notification/audit layer recognises the Activity added event.
Open guide →GuideUnderstand event: Task added
The notification/audit layer recognises the Task added event.
Open guide →GuideUnderstand event: Task completed
The notification/audit layer recognises the Task completed event.
Open guide →GuideUnderstand event: Message added
The notification/audit layer recognises the Message added event.
Open guide →GuideUnderstand event: Document added
The notification/audit layer recognises the Document added event.
Open guide →GuideUnderstand event: Due reminder
The notification/audit layer recognises the Due reminder event.
Open guide →GuideUnderstand event: Overdue reminder
The notification/audit layer recognises the Overdue reminder event.
Open guide →