Understand email failure behaviour | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/licence-applications-understand-email-failure-behaviour Publisher: Pixie Technologies LLC Notifications and audit evidence Understand email failure behaviour Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains that that case/document changes remain saved when email sending fails. Audience: CRM staff; Permission: View/Edit Licence Applications or email administrator; Module v1.0.0; Where to goAdmin Area → Licence Applications → Case → Audit Before you start - Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment. - Verify module activation and the stated permission before attempting the action. - Use a controlled test record for payments, emails, public/portal access, provider calls and deletion. What this guide helps you do 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 - Go to the relevant case or email settings. - Identify the trigger, recipient, subject or audit event described. - Correct contact or SMTP configuration where needed. - Use a controlled new action only after confirming the original record was already saved. Fields and options RollbackNo Evidenceemail_failed audit/log Category/help-centre/category/licence-applications/ Topic/help-centre/topic/licence-applications-notifications-audit/ Rules and limits - The model records email outcomes in audit evidence and does not roll back the case transaction solely because email fails. Check 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. Related guides Understand notification sender selection (https://pixiecrm.com/help-centre/licence-applications-understand-notification-sender-selection)Review licence application audit events (https://pixiecrm.com/help-centre/licence-applications-review-licence-application-audit-events)Notifications and audit evidence (https://pixiecrm.com/help-centre/topic/licence-applications-notifications-audit)Browse all Licence Applications guides (https://pixiecrm.com/help-centre/category/licence-applications)Customers and contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Client portal (https://pixiecrm.com/help-centre/category/client-portal)Compliance Monitor (https://pixiecrm.com/help-centre/category/compliance-monitor)Real Estate Management (https://pixiecrm.com/help-centre/category/real-estate-management)Letter Manager (https://pixiecrm.com/help-centre/category/letter-manager)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)