What to do about Message Processing and Delays, also known as 'Lag,' in Spirion

Spirion Agents communicate with the Spirion Console by sending two main types of messages:

• Status updates – Such as scan progress or heartbeat signals
• Scan results – The location and match results data returned from completed scans

Each message type is placed into a dedicated queue, and the console processes these queues in a first-in, first-out (FIFO) manner. Delays can occur when the volume of messages arriving into either queue exceeds the rate at which the console can process the data. When this happens, users may notice:

• Slower updates to agent status (for example, agents appearing idle or out-of-date)
• Lag in scan results showing up in the console interface

These delays are typically temporary and resolve as the console catches up with the message backlog. The Spirion team is actively working to optimize queue processing and minimize delays, ensuring that data appears in the console as quickly and reliably as possible.

Note: Linux agents, Mac agents, and Windows agents running version 12.6.1 or earlier do not use this queuing system and are not affected by message processing delays.

 If You Suspect a Delay 

If you're noticing delays in agent updates or scan results becoming an issue, we recommend submitting a support ticket so our team can investigate.

To help us diagnose the issue accurately, please include a Gather Data diagnostic file with your ticket. This enables Spirion to determine whether the delay is due to normal message backlog or another underlying issue.