Yes. Simply hover over a widget and click the Info/question mark icon, and a tooltip will show up.

The Vulcan Analytics reports perform a data sync once a day. The analytics mechanism captures and processes data daily around 04:00 AM UTC and updates the reports and widgets accordingly.

This means that the data displayed in the Vulcan Analytics Reports accurately reflects the data captured during the daily sync process (i.e., around 4 AM UTC). Data changes, updates, or settings modifications after the daily is complete are reflected in the reports only after the next data sync (i.e., the next day around 4 AM UTC). If you happen to see some data misalignments when comparing the data in the report to other comparable data sets in the Vulcan Platform, remember that this is expected behavior.

Here are some examples of changes and updates that might occur after the sync time and will not be observed in Analytics until the next sync time:

Nevertheless, the misalignments are usually minor and barely noticeable, with little to no impact on the report's statistical value, validity, and insight.

There is an exception!

The Users and Roles setting is the only element in the Vulcan Platform that syncs in real-time with the Vulcan Analytics Reports. Changes performed on Users and Roles are reflected immediately in the relevant reports and widgets.

Usually no. Analytics sync time is fixed and runs daily around 4 AM UTC. When setting up the Vulcan Platform, connectors and data mergers' daily sync times are set according to the organization's needs.

The difference in sync times between Analytics, Connectors, and data mergers doesn't affect your data as much as it may naturally yield some minor observed misalignments across the platform's comparable data representations.
See An exercise in data validation and what to expect due to Analytics sync time.

No. Any change performed on the Vulcan Platform settings is reflected only in the data processed on the next sync time. Vulcan Analytics doesn't update historical data.

The numbers next to the filter choice selection represent a record in the database table. These numbers have no meaning or impact on the data presented beyond the cosmetic addition to the filters drop-down menu.

Data validation example and what to expect due to Analytics sync time.

Example Goal:
Check and validate the % of Risk Mass in Exception Requests out of the total organization Risk Mass.

Process:
First, let's check the dashboard for the organizational Risk Mass. In this example, it shows 141 m (million).

Next, go to the Exceptions Requests report to check how much of the total organizational Risk Mass is in Exception Requests. You quickly discover that the "Risk Mass in Exception Requests" and the "Risk Mass by Risk Level in Exception Requests" widgets present the needed stats.

A quick addition calculation of the risk mass in each risk level results in 16,472.
​16,472 of 141,000,000 = 0.0001168227% , which validates the % presented in the Risk Mass of Exception Requests widget.
​Note: The percentage fraction representation in the stats is limited to 2 digits. Fractions of % are rounded to the nearest tenth.

So far, so good since the numbers add up.

Now, let's consider the following scenario of a potential observation of data misalignment:

The next day, a connector sync is complete, and more assets are added to the Vulcan platform, with 2 million more risk mass added to the total organizational risk mass. At the same time, you opened 200 more Exception Requests.

If you attempt to re-validate the Risk Mass volume and % in Exception Requests out of the new total Risk Mass before the Analytics syncs again, the numbers will only add up somewhat accurately. In this case, you should expect to observe the same stats in Analytics despite the increase in the organizational overall Risk Mass and the addition of 200 more Exception Requests. The widgets get updated once the Analytics completes daily sync and the numbers align.