Hi Atera Team,

I'd like to request the ability to configure repeating alerts for designated critical devices and scripts.

Current Problem

Currently, Atera sends a single notification when a device or script enters a failed state.

In many environments, that single email can easily get lost among other monitoring alerts or simply among the hundreds of other emails people receive throughout the day. As a result, the customer may never see the notification until much later, allowing a critical issue to go unresolved for hours or even days.

Proposed Feature

Allow any supported object to be marked for repeating notifications.

This could apply to:

PCs
Servers
Generic Devices
Scripts

For example:

Repeat alert every: 15 minutes, 30 minutes, 1 hour, 2 hours, etc.

The repeat notifications would continue until the device or script returns to a healthy state.

Suggested Implementation

Atera already allows us to choose which notifications we receive, such as Critical and Resolved alerts.

It seems like the most natural place for this feature would be in that same notification configuration area. For example, a simple option such as:

☐ Repeat this alert every: ___ minutes until resolved

This would fit naturally into the existing alert configuration without changing the current workflow for users who don't need the feature.

Example

I monitor customer camera systems.

Some alerts are informational, but others are extremely important.

Examples include:

Camera Server offline
RAID array failure detected by a custom script
Core network equipment offline

If the original email is overlooked or buried in the customer's inbox, the customer could unknowingly operate for hours or even days with a critical failure. Repeating notifications at a configurable interval would greatly increase the likelihood that the issue is noticed and addressed promptly.

Expected Behavior
A critical device or script enters a failed state.
Atera immediately sends the initial notification.
If the device or script remains in the failed state, Atera sends another notification at the configured interval.
This continues until the issue is resolved.
Once the device or script returns to a healthy state, Atera sends the normal recovery notification and stops the repeating alerts.
Benefits
Prevents critical alerts from being forgotten or overlooked.
Helps ensure outages are resolved more quickly.
Gives customers confidence that important failures won't disappear into their inbox.
Allows repeating notifications to be enabled only for the devices and scripts that truly require them, preventing unnecessary email traffic.
Gives customers flexibility to decide which devices and scripts warrant persistent notifications and which only need a single alert.

This feature would work especially well alongside an "Only Alert if Offline for X Minutes" request that I also made here. Less important or unstable devices could wait before generating an alert, while truly critical devices and scripts could continue reminding users until the issue has been resolved.

Thank you for considering this request. I believe this would significantly improve Atera's monitoring capabilities for businesses that rely on timely notification of critical infrastructure failures.