Problem
Alerts in Visual Command Center (VCC) are showing the incorrect radius.
Root Cause
There are two common causes:
VCC default radius settings: By default, the radius for alerts in VCC is set to 16 km. If the radius displayed is incorrect for any particular feed, the radius settings for that feed must be reconfigured in VCC.
Additionally, VCC alert settings and CEM Orchestration workflows are configured separately. This means:
An alert in VCC could be configured with one radius (for example, 5 miles) for showing affected assets, while an orchestration workflow filter could use another (for example, 0.5 miles) for triggering automated actions.
Solution
Two examples of feeds that can generate alerts are the Everbridge Advisories and Everbridge Risk Events feeds. Each data feed is branched separately so that alert settings can be managed independently. For this example, follow the steps below to configure Civil Unrest alerts for feeds as desired:
Log in to Visual Command Center.
Select the menu icon on the upper right-hand corner.
Select Admin Console.
Select Data on the right side of the page.
On the left, scroll down and click on either Everbridge Advisories or Everbridge Risk Events.
Scroll down to find Civil Unrest and drag the slider to adjust the radius as desired.
Make any other needed changes.
Click Save.
NOTE: Other feeds may be actively alertable. As a best practice, go through each alertable data feed and adjust the settings as needed.
To confirm which orchestration workflow and radius were actually applied when an alert was triggered, use the following checks in CEM Orchestration:
Include workflow or ruleset variables (such as workflow name and radius) in your alert template so that each alert clearly shows which workflow fired and what radius it used.
In the CEM Orchestration activity log, enable the option to show entries with no actions taken so you can see all evaluated workflows, including those that matched but did not execute actions.
If an activity log entry references a workflow ID that no longer exists or has been modified, that indicates a previous version of a workflow (with different radius criteria) may have triggered the alert at the time.
Workaround
If you cannot immediately align or update all VCC feed settings and CEM Orchestration workflows, you can still validate behavior and reduce confusion by:
Temporarily setting the same radius value in both VCC alert settings and the corresponding orchestration workflows for the feeds you most frequently use.
Using alert templates that display the workflow name and radius used at trigger time, so any apparent mismatch between the plotted circle and your expected value can be quickly explained.
Reviewing recent workflow edits before troubleshooting radius mismatches, especially if workflows were renamed, modified, or deleted shortly before the alert occurred.