Purple Ingest Notifications

user guide for configuring and receiving notifications from purple ingest overview purple ingest sends notifications to keep you informed about your content processing always on notifications (automatic when email addresses configured) job completion when content processing succeeds, fails, or completes with warnings import errors when file processing encounters validation or parsing errors optional file alarms (require alarm enabled true ) expected issue alarm sent at expected date (before publication) when file hasn't been uploaded missing file alarm sent at publication date when file still hasn't been uploaded all notifications are sent via email to addresses you configure per team currently, only email notifications are supported, but additional notification channels may be added in the future configuration adding email recipients to receive notifications, configure email addresses in your team's config yml file emailaddress \ admin\@example com \ team\@example com key points emailaddress list of email addresses to receive all notification types (required) all notification types use the same recipient list multiple recipients are supported email addresses are sent via bcc for privacy (recipients don't see each other) email addresses can only be configured at root level all paths use the same recipients to enable file alarms, additional configuration is required (see optional file alarms section) for complete configuration file documentation, see the notification types always on notifications these notifications are sent automatically whenever you configure email addresses no additional settings are required they work as soon as you add recipients to the emailaddress field 1\ job completion notifications sent when a content transformation job finishes processing when sent success job completed without errors partial success job completed with warnings, issue is already published partially processed job completed with warnings, issue not yet published failure job failed due to errors email content success import information (publication, issue, dates, files) link to ingest monitoring partial success import information (publication, issue, dates, files) general action items open ingest monitoring to view detailed warnings review each warning to determine if action is needed verify content renders correctly despite warnings link to ingest monitoring partially processed import information (publication, issue, dates, files) general action items open ingest monitoring to view detailed warnings review each warning to determine if action is needed verify content renders correctly despite warnings link to ingest monitoring failure import information (publication, issue, dates, input file) detailed error message explaining what went wrong link to ingest monitoring what to do success notification verify the issue in content cloud confirm content renders as expected (only possible if the publication date is already reached) partial success notification open ingest monitoring to view detailed warnings review each warning to determine if action is needed verify content renders correctly address any critical warnings for future uploads partial processed notification open ingest monitoring to view detailed warnings review each warning to determine if action is needed verify content renders correctly once published address any critical warnings for future uploads failure notification read the error message carefully check that the input file is valid and not corrupted review metadata or configuration for errors fix the issue and re upload the file confirm success notification arrives after re upload 2\ import error notifications sent when file processing encounters validation or parsing errors when sent immediately after file is processed (csv, epub, name scheme, or sb archive batch) only sent if errors are detected during parsing or validation for sb archive sent once per batch with all errors from all processed folders email content team id and filename (or batch name for sb archive) detailed list of all errors found (line numbers for csv, metadata issues for epub, folder specific errors for sb archive) link to ingest monitoring what to do review each error carefully fix the errors in your file or metadata re upload the corrected file confirm no error notification arrives after correction common errors csv collector invalid date format use supported formats (yyyy mm dd, dd mm yyyy, dd/mm/yyyy) publication not found ensure the publication exists in purple publish and name matches exactly missing required columns include folder, publication, issue name, publication date duplicate entries each issue name + publication combination must be unique invalid access type use free , paid , or locked epub collector publication not found ensure the epub title exactly matches an existing publication name in purple publish missing metadata epub must contain required dublin core metadata fields (dc\ title, dc\ date) invalid date format publication date in epub metadata must be valid invalid epub structure epub must contain valid package opf file name scheme collector invalid filename pattern filename must match configured pattern publication not found publication code in filename must match existing publication sb archive collector no mets xml found each issue folder must contain a mets xml file with edition metadata edition not found in mets xml mets xml must contain parseable edition information invalid folder name format folder names must follow pattern yyyymmdd edition sequence (e g , 20250115 ed1 0001 ) no publication mapping edition code from mets must exist in publications configuration publication not found publication name must exist in purple publish and match exactly no files for zip issue folder must contain at least one file besides mets xml zip creation failed check s3 permissions and connectivity optional file alarms file alarms monitor for missing or late files and must be explicitly enabled by setting alarm enabled true in your configuration unlike always on notifications, file alarms require both email addresses and the alarm configuration when sent both alarm types monitor for files that haven't been uploaded in time, triggered at different stages expected issue alarm sent when expected date is reached (configured via alarm start , default 1 hour before publication date) file hasn't been uploaded yet checked every 5 minutes only sent once per issue missing file alarm sent when publication date is reached file still hasn't been uploaded checked every 5 minutes only sent once per issue configuration emailaddress \ admin\@example com alarm enabled true start 1h end 24h alarm configuration fields alarm enabled enable or disable file alarms ( true or false ) alarm start time before publication date when file is expected (e g , 2h , 30m , default 1h ) alarm end stop sending alarms this long after publication date (default 24h ) time format 30m = 30 minutes 1h = 1 hour 2h = 2 hours 24h = 24 hours important alarm settings can only be configured at root level and apply to all paths within your team email content both alarm types include import information (publication, issue, dates, input file name) action items to check whether the issue has been created in your cms whether the export to sftp has been triggered whether the uploaded file has the correct name whether the file is in the correct folder link to ingest monitoring what to do when you receive a file alarm check if the file was actually uploaded to the correct folder verify the filename matches the expected name confirm the file is in the correct path check if the cms export completed successfully upload the file email format all emails include subject clear indication of notification type and affected issue import information publication, issue name, dates, and filenames error/warning details specific information about issues (when applicable) action items checklist of steps to investigate or resolve ingest monitoring link direct link to view the job details emails are sent in both plain text and html format for compatibility with all email clients recipient privacy all recipients are sent via bcc (blind carbon copy) recipients cannot see other email addresses one email is sent with all recipients in bcc troubleshooting not receiving notifications check configuration emailaddress \ your email\@example com alarm enabled true start 1h end 24h common issues email field is empty or missing add at least one valid email address to root config invalid email format ensure emails contain @ and valid domain file alarms disabled check that alarm enabled is set to true in root config spam folder check spam/junk folders for emails from noreply\@purplepublish com receiving duplicate notifications possible causes same email in multiple teams same email address configured in different team configurations misconfigured email lists email address appears multiple times in the same list solution review your team's root configuration file ensure email addresses are only listed once in the emailaddress field configuration examples basic setup single admin receives all notifications emailaddress \ admin\@dailynews com alarm enabled true start 1h end 24h team setup multiple team members receive notifications emailaddress \ editor\@magazine com \ production\@magazine com \ admin\@magazine com alarm enabled true start 2h end 24h multi path setup all paths use the same email recipients from root configuration root team id/config yml emailaddress \ general\@publisher com alarm enabled true start 1h end 24h note email addresses and alarm settings apply to all paths use a shared email address or distribution list if you need different people to receive notifications for different content see the for details on other per path configuration options (collector, convert, upload) different alarm timings adjust alarm windows based on your publication schedule tight deadline (e g , daily publication) emailaddress \ team\@publisher com alarm enabled true start 1h end 24h longer window (e g , weekly publication) emailaddress \ team\@publisher com alarm enabled true start 2h end 48h note since alarm settings apply to all paths, choose timing that works for your most critical publications no alarm setup receive job completion notifications but no file alarms emailaddress \ team\@news com alarm enabled false best practices email address management ✅ do use team email aliases (e g , team publishing\@company com ) include key stakeholders only use distribution lists for larger teams keep email list updated as team members change ❌ don't add personal emails that might become inactive include external partners without approval use catch all addresses that might ignore alerts add too many recipients (keep it focused) alarm configuration ✅ do set alarm enabled true to receive file alarms set alarm start based on your workflow (default is 1h , but 1 2 hours is typical for customization) set alarm end to stop alarms after reasonable time (default is 24h ) account for timezone differences in your publication schedule test with your actual publication schedule document expected dates in your configuration ❌ don't set alarm start too early (causes false positives) set alarm start too late (doesn't give time to react) set alarm end too short (might miss late issues) ignore file alarms (they indicate potential issues) disable alarms without understanding the impact response workflow summary notification type priority action success ✅ low verify in content cloud partial success ⚠️ medium check warnings in ingest monitoring, verify published issue partially processed ⚠️ medium check warnings in ingest monitoring, verify when published failure 🔴 high fix error and re upload expected issue alarm 🟡 medium upload missing file missing file alarm 🔴 high upload missing file urgently import errors 🟡 medium fix file/metadata and re upload support for issues with notifications check configuration verify emailaddress field is set correctly and alarm enabled is true for file alarms check spam folder emails from noreply\@purplepublish com contact support include team id, issue name, and timestamp