Clients can receive notifications for processing errors. Some of the errors are specific to, and therefore documented with, specific workflows. For example, notifications specific to the renewal workflow are documented with that page. This page documents notifications that apply to both new and renewal business workflows.
- Navigate to Settings > System Wide > Administrative Alerts > Processing.
- Designate recipients in the Processing Errors.
Note: The Processing Errors administrative alert sends at least five different emails, three of which are documented on this page.
Nightly processing errors
Recipient(s) receive an email (example below) regarding any error in processing that could have occurred.
BriteCore Alert: Nightly Processing Errors[information related to error, usually code]
Deliverable creation errors
Recipient(s) receive an email (example below) with a list of deliverables that BriteCore could not generate during normal processing. In most cases, clients will need to access the policy in BriteCore and regenerate the deliverable.
Deliverable Creation Error: [carrier name]
Policy 10-2017-1 failed to generate [name of deliverable]. Exception: [detail of error]
Bail Out!: [carrier name] [name of deliverable] deliverable failed to generate: [reason for failure]
Recipient(s) receive an email (example below) when an error occurs with an integrated vendor.
BriteCore Alert – Dropbox enabled but not authorized.
Dropbox integration for print job backups is enabled in BriteCore but not authorized. Please visit [URL] to authorize BriteCore to upload print job backups to your account.
BriteCore Alert: Nightly Vendor Upload Errors
Traceback (most recent call last):[code] [error, such as KeyError: ‘hostIP’, error: [Errno 111] Connection refused or error: [Errno 104] Connection reset by peer]
BriteCore Alert: Ambiguous ISO Protection Class
The following policy could not determine an ISO Protection Class for the property “Property 1”. Please choose a new one, then rate and commit the policy manually.