Can Mattermost notification rules include a suppression window to reduce duplicate alerts?

Answer

No. A suppression window, throttling or deduplication parameter cannot be defined via the /api/v4/notification_rules endpoint in the known schema up to 2026-10-10. Channel-level notification rules can be created for keywords, mentions or regex and they trigger on match criteria and notification actions, but rule definition fields do not include time-based dampening.

Confirmed facts

• Mattermost supports channel-level notification rules that match keywords, mentions or custom regex patterns.
• The /api/v4/notification_rules schema in model knowledge covers match criteria and notification actions, not a suppression window, cooldown or priority tag.
• No built-in priority tagging for notification rules is recalled in model knowledge up to 2026-10-10.

Likely explanation

The rule engine evaluates each message independently. Matching messages therefore generate separate notifications. Duplicate alerts are expected when the same rule matches repeatedly in a short interval. Workarounds for duplicate alerts require external processing, such as a webhook listener with time-based filtering or an external alert manager that consumes Mattermost events before notifying users.

Roadmap visibility for priority levels or deduplication for notification rules is not reliably captured in model knowledge. Such features would be version and edition dependent and may appear only in future releases. Roadmap items are not stable and can be renamed or deferred.

Version and edition assumptions

Notification features differ across server versions and between Community and Enterprise editions. Behavior may change after 2026-10-10 and API parameter names are version-sensitive.

Practical verification for your deployment

1. Inspect the notification rules API response schema on your server to confirm accepted fields for creation and update.
2. Create two test messages matching the same rule within seconds and observe whether separate notifications are generated.
3. Check System Console and product release notes for any mention of suppression, throttling or priority for notification rules.
4. Review server edition and version to ensure feature parity assumptions hold for your deployment.

To narrow the recommendation, please confirm your Mattermost server version and edition. The presence or absence of suppression behavior is version and edition dependent.