Archiving Alerts
To keep your system organized and free of clutter, you can archive alerts that are no longer in use.
Archiving hides these alerts from your daily view while keeping their configuration safe in the background, so you don't have to delete them permanently.
What can be archived?
You can archive most standard alert types, including:
• Actions
• Alarms
• Notifications
• Notify-once notifications
• Event-based notifications
How it works
• Preparation - Before you can archive:
◦ an alert, you must first set its status to Disabled.
◦ an event-based notification, ensure that no active status transitions are linked to it in Field Definer. To identify any linked status transitions, check the Status transition detail field on the event-based notification record. This field lists the status transitions currently configured to trigger the notification. Remove or deactivate these links before archiving the notification.
• Visibility: Once archived, the alert is hidden from your list. You can use the Show/hide archived items option if you ever need to see or restore them.
• Safety Lock: Archived alerts are read-only. This means they cannot be changed unless you de-archive them first, preventing accidental edits to historical settings.
What happens to the system?
• Automatic Stop: The system automatically stops processing archived alerts. They are removed from the scheduling queue within about a minute of being archived.
• Clean Up:
◦ For Alarms: Archiving an alarm automatically clears out any old alarm notifications (including snoozed or forwarded ones) so they don't stay stuck on your dashboard.
◦ For Event-based notifications: If you archive a notification that is triggered by a specific event (like a status transition), the system will also clear out any pending tasks related to that notification.
• Configuration Transfer: Archived alerts are kept local to your environment. They won't be included when you export configurations to another system, ensuring your target environment stays just as clean.