Alarm redirections can be triggered automatically, manually, or both (see Understand Alarm Redirection). However, ClearSCADA will not trigger alarm redirections on any:
- Alarms that do not meet all of the redirection criteria (the criteria is configured on the Redirection tab of the relevant configuration Forms—see Configure Alarm Redirections for an Item or Group)
- Alarms that are disabled (see Disable Alarms in the ClearSCADA Guide to Alarms)
- Alarms that are suppressed (see Alarm Redirection and Suppressed Alarms)
- Items or Groups for which the CancelRedirections method is used to abort alarm redirections (see CancelRedirections and RestartRedirections Methods)
- Items or Groups on which specified redirection Action, Action Roster, and alarm redirection Calendar is inactive. (As with most database items, a redirection Action, Action Roster, and alarm redirection Calendar needs to be In Service in order to be active on the system.)
- Lone server systems on which the server is shut down while alarm redirections are in progress. On lone server systems, any pending alarm redirections will be lost and the intended recipients will not be notified. (On multi-server systems, the alarm redirections will still be sent to the recipients, but from the Standby server that goes Main.)