Understand failed email status | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/service-journeys-notifications-email-cron-failed Publisher: Pixie Technologies LLC Notifications, email logs and cron automation Understand failed email status Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Failed attempts retain error evidence for retry. Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicants; Permission: Administrator; Module v1.0.0; Where to goCRM cron → Service Journeys notification processor Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do Failed attempts retain error evidence for retry. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to CRM cron → Service Journeys notification processor. - Find the record, endpoint, field or action used to understand failed email status. - Complete the displayed values exactly as described in this guide. - Select the available save, submit, send, upload, create, update or confirm action. - Return to the related register, portal, activity log or API response and verify the expected result. Fields and options Workspace or endpointCRM cron → Service Journeys notification processor PurposeFailed attempts retain error evidence for retry. Rules and limits - The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions. - Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages. Check it worked - The understand failed email status workflow completes without a validation, permission, ownership or availability error. - The related record, portal view, activity entry, notification log or API response shows the expected state. - Client-visible, public and API data remains limited to the code-backed ownership and visibility rules. Security, privacy and operational checks - Use controlled test records and non-production credentials before wider rollout. - Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs. Related guides Understand immediate email attempts (https://pixiecrm.com/help-centre/service-journeys-notifications-email-cron-immediate)Understand retry limit (https://pixiecrm.com/help-centre/service-journeys-notifications-email-cron-retry-count)Notifications, email logs and cron automation (https://pixiecrm.com/help-centre/topic/service-journeys-notifications-email-cron)Browse all Service Journeys guides (https://pixiecrm.com/help-centre/category/service-journeys)Projects, tasks and time tracking (https://pixiecrm.com/help-centre/category/projects-tasks)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Create a task (https://pixiecrm.com/help-centre/create-a-task)Upload and share customer files (https://pixiecrm.com/help-centre/upload-and-share-customer-files)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Review email delivery issues (https://pixiecrm.com/help-centre/review-queued-email-and-delivery-issues)