Question
Why are Everbridge Risk Events shown as closed in Visual Command Center (VCC) when they are known ongoing events, and why might they not generate new incident notifications after 24 hours?
Answer
In VCC, Everbridge Risk Events and the incidents created from them follow specific auto-expiration and auto-acknowledge rules, which can make an event appear closed even though the underlying situation is still ongoing.
Auto-close when no end date or updates: Everbridge Risk Events that are created with no explicit end date will automatically close after 24 hours if no updates are received from the Everbridge Risk Intelligence Monitoring Center (RIMC). This behavior is by design to prevent the Risk Events feed and map from being inundated with long-running events that are not actively updated.
Auto-acknowledge and incident closure: Separately, if a Risk Event does not receive an update within 24 hours in the VCC application, it is auto-acknowledged. When auto-acknowledge occurs, any incident that was created from that Risk Event is closed.
What happens if an update arrives after 24 hours:
The Risk Event itself remains able to receive updates. If an update is received after the 24-hour expiration/auto-acknowledge period, the Risk Event will reopen and be marked with a status of "updated".
However, incidents that were closed by auto-acknowledge are not re-opened, and therefore they will not generate additional incident notifications for any subsequent Risk Event updates.
Why an event might show as closed while impacts continue: In some cases, RIMC or a feed provider may close a high-level or "parent" Risk Event (for example, a nationwide storm) once the main hazard has dissipated, even though related impacts (such as local power outages, flooding, or infrastructure damage) are still being tracked. Those residual impacts may be monitored and updated as separate Risk Events, so the original storm event can show as Closed while related disruption events remain active or are updated independently.
Why the description might not reflect later developments: If new information (such as a later-reported fatality) becomes available after a Risk Event was closed by RIMC, the original published event may not be updated to incorporate that new detail. In those situations, VCC can continue to display the original description even though the real-world situation evolved after closure.
Because of this design, you may see a Risk Event continue to receive updates (or appear as updated) while the associated incidents and notifications remain closed, even if the real-world situation is still ongoing, or see a closed Risk Event whose summary does not reflect information that emerged after the event was closed.