Notification Flood Control

Notification flood control prevents users from being flooded with multiple notifications from a workflow or integration when they've already been notified about an incident and are working on resolving the issue. You can use this feature to control the maximum number of notifications that are delivered to specific device types during a defined period, such as: no more than two messages every ten minutes to SMS and mobile app devices.

Notification flood control is a company-level setting that applies only to individual workflows or inbound integrations which have it enabled. The default configuration settings for this feature limit notifications to one message every three hundred seconds (or one message every five minutes) to mobile app, chat app, SMS, and voice device types.

For example, imagine that an incident occurs that triggers a flow or integration in xMatters. You receive a notification on the mobile app, but before you can address the problem, the incident causes something of a chain reaction in your system, setting off multiple incidents that all trigger the same flow. Luckily, you already enabled notification flood control for that workflow to limit notifications to mobile app and SMS devices to no more than two messages every ten minutes.

So, while it takes you half-an-hour to resolve the original incident and get your system back to normal, you only receive a couple of messages every ten minutes on your mobile app - allowing you to keep an eye on the overall progress of the incident while still being able to deal with the problem at hand. You can check your email later to see all of the messages that xMatters sent in response to the incidents, but you don't have to deal with them in the heat of the moment.

Configure notification flood control

This section describes how to configure company-level notification flood control settings which are applied to individual workflows (or to individual inbound integrations within a workflow). For instructions on how to enable notification flood control for your workflow or integrations, see Enable notification flood control.

When enabled, notification flood control applies to notifications that target users directly, via subscriptions, or through activity updates. If a user previously received notifications from a workflow or integration by any of these methods, xMatters will suppress any additional notifications from these methods that exceed the specified notification flood control settings for the selected device types.

Notification flood control also overrides the 'Allow Duplicates' setting for groups, suppressing duplicate notifications sent to the same device type of a particular user based on their membership in more than one group.

If xMatters fails to deliver a notification, it will automatically try again; retries are not suppressed, even if they would otherwise be subject to notification flood control.

The Alerts report and Log report indicate alerts where notifications were suppressed.

In logs and activity panels, notification flood control will appear as false when the alert is initially generated. This is because alerts are created before notifications are sent, so there is nothing to suppress at alert creation. Once notifications are generated and sent, the logs and activity information is updated with whether or not the notifications were subject to flood control.

Enable notification flood control

By default, notification flood control is disabled for all workflows. You must enable notification flood control for individual workflows. When notification flood control is enabled for a workflow, it applies to all flows and inbound integrations within that workflow. You can optionally enable notification flood control for individual inbound integrations without enabling it globally for the workflow the inbound integration is contained in.

The following sections describe how to enable notification flood control for workflows and inbound integrations.