Visual Command Center (VCC) uses orchestration workflows to control when alerts are created and notifications are sent for Travel Risk Events. Understanding how these workflows operate helps you manage which events generate alerts and why some expected alerts may not appear.
Overview
Alert creation for Travel Risk Events in VCC is driven by orchestration rules (workflows) associated with the Travel Risk Events feed. These workflows:
- Evaluate incoming Travel Risk Events against defined logic
- Create alerts when configured conditions are met
- Trigger notifications based on the same workflow configuration
When the relevant workflow for a given feed is enabled, VCC continuously evaluates Travel Risk Events and applies the specified actions, such as creating alerts or sending notifications.
How alerts for Travel Risk Events are created
Alert generation for Travel Risk Events depends on the workflows tied to the Travel Risk Events feed. When the appropriate workflow is active:
- VCC receives a Travel Risk Event from the feed.
- The event is evaluated against the workflow’s conditions.
- If the event meets the defined conditions, VCC creates an alert.
- Notifications are sent according to the workflow’s notification configuration.
If the workflow’s conditions are not met, no alert or notification is generated for that Travel Risk Event.
Why alerts might not be generated
Several configuration issues can prevent alerts from being generated for Travel Risk Events, even when you expect them:
- Workflow for the Travel Risk Events feed is turned off: If the workflow associated with the Travel Risk Events feed is disabled, VCC will not create alerts for these events. This applies even if there are tracked people or assets in the affected area.
- Other workflows may still be active: Other workflows unrelated to the Travel Risk Events feed may remain enabled and continue generating alerts, which can make it seem like alerts are working in general while specific Travel Risk Event alerts are missing.
- Geographic or condition mismatch: The workflow’s conditions, including geographic filters, may not match the events or areas where you expect alerts, resulting in no alerts being created.
To restore alert creation for Travel Risk Events, review the orchestration rules or workflow configuration associated with the Travel Risk Events feed and enable the workflow or workflows responsible for creating alerts.
Always-on alerts and alerts without nearby assets or travelers
VCC can be configured to generate alerts even in locations where you have no assets or travelers. This occurs when a workflow action is configured as Always Alert for a specific event category.
For example, if a “Crime” workflow is tied to the Everbridge Travel Risk Events category and its action is set to Always Alert, the system will create an alert every time a crime event in that category is received, regardless of whether assets or contacts are in the affected area.
If you receive alerts that are not relevant to your assets or travelers:
- Review the workflows that apply to the affected event category.
- Identify any actions set to Always Alert.
- Adjust those workflows to change the action from Always Alert or add filtering conditions so alerts are created only when matching assets, contacts, or other criteria are present.