Skip to main content
Feedback

Email Alerts overview

You can add, edit, and delete email subscriptions to receive email reports of runtime status, process execution status, and/or user notifications. You can add these alerts for any of the Boomi accounts you can access with your user name.

Email Alerts configuration window

The Email Alerts tab has two sub-tabs - the Integration sub-tab, and the Hub sub-tab, which is only visible for accounts with Boomi DataHub enabled. They monitor Integration and Boomi DataHub activity, respectively.

The information in the remainder of this topic and its subtopics relates to subscriptions to Integration activity. Refer to Adding an email alert for information about subscriptions to Boomi DataHub activity.

Subscription Types

  • For a given subscription, you can choose the type of event about which you want to be notified and the severity level:

    • The event types are ATOM.STATUS, PROCESS.EXECUTION, USER.NOTIFICATION, or ALL, which includes all three event types.

    • The logging levels are INFO, WARNING, or ERROR. For example, you may want to receive INFO logging-level emails about runtime status, and ERROR logging-level emails about process executions. Or perhaps one person in your company may want to only receive emails about runtime status and another person may want to receive only emails about user notifications. INFO-level subscriptions also include WARNING and ERROR level alerts.

  • Every 15 minutes, Integration polls the accounts in the Alerts list. Depending on your Log Level settings, Integration sends the proper email alerts for the event type(s) to which you are subscribed.

  • All alerts that are reported within a 15-minute period are grouped by event type and sent in one email. When a user sets a time zone on the User Information tab, messages use that time zone for dates and times.

    note

    If your account generates an unusually large volume of events during a single 15-minute interval, the platform may send additional emails to fully report all events that occurred.

  • Low latency processes do not generate email alerts. Generally, any processes run on the execution worker are low latency and therefore do not generate email alerts. For Web Services Server listeners that use Low Latency Debug on the Cloud, General mode HTTP calls also do not generate email alerts.

  • Email alerts set up before an event type is selected are subscribed to ALL event types. To change the event selection, delete the existing email alert, then create a new email alert that is subscribed to the event type at the logging level about which you want to be notified.

  • Processes deployed—and runtimes attached—to environments with the Test classification do not generate email alerts about executions or about the status of runtimes. However, you do receive RSS feeds, and you can use the Event object in the API to query notifications.

Atom Status alerts

The ATOM.STATUS alert identifies a recorded time when a runtime in the account is online or offline.

  • Online — This status is sent for the INFO log level when runtimes are down and then started.

  • Offline — This status is sent for the INFO through ERROR log levels when runtimes go down or are disabled.

    The Boomi Enterprise Platform detects that a runtime is offline when it does not receive communication from the runtime for more than a minute (typically, a down runtime can be detected as early as 45 seconds and as late as four minutes). The runtime status alert system monitors for status changes in 15 minute intervals, and then issues an email if a runtime status change was detected.

    info

    Runtime alerts that occur sooner than a minute may indicate a temporary network interruption, rather than a true outage.

    To determine if a runtime outage has occurred or is occurring, visit the Runtime Information tab of the Runtime Management page to confirm the runtime's status and the Startup Properties tab to view the runtime's last restart time to verify whether an outage occurred and recovered.

    For example, an alert schedule runs at the top of every hour starting at 12:00 A.M., and monitors for status changes at 12:15, 12:30, 12:45, and so on. If the platform recognizes that a runtime is offline at 12:01, the status isn't sent until 12:15 per the schedule, about 14 minutes later. In the same scenario, the runtime is offline at 12:14 A.M. and the alert is issued only a minute later at 12:15. The cadence in which this schedule runs explains why runtime status emails are received at varying times in relation to when a runtime is offline.

Process Execution alerts

The PROCESS.EXECUTION alert identifies the start and end time for the execution of a runtime's process. The number of inbound and outbound documents are recorded, along with any documents that may have encountered errors during the process execution. The alert includes the process’ execution ID and a link to the execution. Clicking the link takes you to the process on the Process Reporting page. INFO log level alerts always send an execution status if the process runs to completion. Accompanying warning and error alerts can also be logged, depending on your process flow.

This INFO log level alert indicates that the process has completed:

This ERROR log level alert indicates that the process has an error:

You can use the Exception step in your process flow to trigger PROCESS.EXECUTION alerts. You can also use the Exception step to send a customized message for the first document that encounters an error and to stop all or any documents that reach this step.e.

User Notification alerts

The USER.NOTIFICATION alert identifies a Notify step having the Enable Events option that was included in a process execution. The message level (Info, Warning, or Error) set in the Notify step affects the type of email alert that is sent, but it does not stop a document or set of documents from processing to completion. The Title and Message fields in the USER.NOTIFICATION alert display the results of those configurable fields in the Notify step:

On this Page