Understand email failure behaviour

This guide explains that that case/document changes remain saved when email sending fails. 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.

What you’ll accomplish

Know that case/document changes remain saved when email sending fails. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

1. Go to the relevant case or email settings.
2. Identify the trigger, recipient, subject or audit event described.
3. Correct contact or SMTP configuration where needed.
4. Use a controlled new action only after confirming the original record was already saved.

Fields and options to review

Rules the system enforces

• The model records email outcomes in audit evidence and does not roll back the case transaction solely because email fails.

How to confirm it worked

• Understand email failure behaviour completes through the supplied module flow.
• Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.

Security, privacy and operational checks

• Use the least-privilege account that has the stated permission.
• Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.

Continue with related guidance