Titan Cloud Edge categorizes alarms into Active and Historical. While at the most basic level it can be assumed that Active alarms are Uncleared in the ATG and Historical alarms are Cleared, exceptions can occur. 

Some common examples of scenarios that cause discrepancies include but are not limited to: 

• Veeder Root ATGs require separate commands to retrieve active and historical alarms, and can provide conflicting data.
• An ATG can only hold the last 100 alarm events, so a faulty sensor or other issue causing hundreds of events in a short time can cause previous alarms to get lost or stuck.
• ATG connectivity outages or maintenance events can keep active alarms from clearing until polling is restored. 
  • If ATG memory is cleared, new equipment is installed, or more than 100 alarm events occur between successful polls, the previously polled active alarms may get “stuck” without a historical alarm record. 

In cases where an alarm has been cleared in the ATG but still appears as active in Titan Cloud Edge, users can manually clear the alarm from the grid in the Alarms page.

Use the filters to locate the desired alarm(s) in the grid. 

Use the checkmarks in the Mark as Cleared row to designate the alarm(s) that should be cleared. You may also choose to click the checkbox in the column row to mark all alarms as cleared. 

Scroll to the bottom of the page and click Update. The changes will save, but you may need to refresh the page to see them removed from the grid.

Note: If you manually mark an active alarm as cleared but it has not been cleared in the ATG, it will return to the grid after the next poll with a record of the manual clearing event.