Devices record shuns as they occur. However, devices only report shuns back to Risk Analytics servers in batches. This is necessary both for reliability and efficiency, as explained in the next two paragraphs.
A power failure will not result in loss of recorded shun data. Interruptions in network service result in delayed reporting of shun activity. Although devices on average report shuns within minutes, delivery can be delayed by tens of minutes or more under adverse network conditions. Eventually, the shuns will be reported.
Because devices support wire-speed shunning, large numbers of shun events may be recorded. This means that batching is required to reduce communications overhead. Billions of recorded shuns are processed each month by Risk Analytics servers. RAForce routinely aggregates millions of shun records when generating different views.
Due to the asynchronous nature of shun reporting, discrepancies can appear at various times. For instance, if you are subscribed to an email report, the contents of that email reflect the state of the shun database at that point in time. Viewing the same data in RAForce might show additional data that did not appear on the report. Although we have taken care to design our systems to minimize the apparent differences between generated reports and the live view of reported data in RAForce, we cannot guarantee that newly reported data will not have arrived after the fact. RAForce will always display the latest data that is available to it.