Orphaned Alarms
It is rare but possible for an alarm to become "orphaned" during application development. For example, the following (completely contrived*) set of steps might lead to an orphaned alarm:
- Create an alarm and allow it to activate.
- Export the tag database to Excel.
- Remove the activated alarm tag.
- Set the property, AlarmDatabasePurgeDelay to a high value to delay VTScada's automatic clean-up process.
- Restart the application.
- Import the spreadsheet containing the modified tag list.
- From the Alarm Page, open the details dialog for the alarm.
Use this dialog to remove the alarm from the lists. In most cases, it is advisable to remove orphaned alarms from all lists. Confirmation is required. (No record can ever be removed from the history list, but if a tag was deleted, the record will show only its unique ID. This is done to avoid confusion with any new tag that you might create using the same name as the deleted tag.)
(*) These steps are not recommended practice, and there is no guarantee that they will succeed in creating this situation, which is undesirable in any event. The steps are provided only to give a sense of how an orphaned alarm might come to be.
