How to read the Agent LAGGED Report

The Agent LAGGED Report surfaces two things at once: which servers recorded lag events during a date and time range, and which individual Agent sessions were caught lagging. If your dialer is producing stale screen updates or agents are reporting that their screen "froze" for a second before catching up, this report gives you the raw evidence to figure out where the problem lives.

What a LAGGED event means

VICIdial tracks the timing between the server sending a status update and the Agent screen acknowledging it. When that round-trip takes longer than the allowed threshold, the system logs the event as LAGGED. A single LAGGED event is not alarming — brief network hiccups happen. A cluster of them on one server or repeated events tied to the same agent are the patterns worth chasing.

Lag at the server level usually means Asterisk or the database is under pressure. Lag isolated to one user usually means their workstation, browser, or local network is the bottleneck, not the server.

The two sub-reports side by side

The report page loads two tables for the selected date and time range.

• Server summary table — one row per server IP, showing the total count of LAGGED events on that server for the window. This is your first filter: if all events land on one server IP, that box is the problem. If they spread evenly across all IPs, it is more likely a network or time-of-day issue affecting the whole cluster.
• Detail table — one row per LAGGED event, listing the agent log ID, user ID, server IP, the exact event time, the lead ID being worked, the campaign, the call status at that moment, the user group, the dial method in use, and the unique ID of the call leg. This is the evidence trail that lets you link a lag spike to a specific call and agent.

How to read the detail table

Sort the detail table by event time and look for bursts — several events within a short window are a stronger signal than the same count spread over hours. Note the campaign column: if LAGGED events cluster around one campaign, check whether that campaign's Dial level is set unusually high and is hitting the box hard.

The user ID column is the key for separating server problems from endpoint problems. If ten different user IDs appear in a one-hour burst on the same server IP, the server is the suspect. If one user ID accounts for most events and the server IP varies, the problem follows that person's workstation.

Decision path after reading the report

flowchart TD
  A["Open Agent LAGGED Report"] --> B["Check server summary table"]
  B --> C{"Events concentrated on one server IP?"}
  C -->|Yes| D["Inspect server load and process count"]
  C -->|No| E{"Events tied to one user ID?"}
  E -->|Yes| F["Check agent workstation and browser"]
  E -->|No| G["Check network segment or time-of-day load"]
  D --> H["Lower dial level or resize server"]
  F --> I["Ask agent to clear cache or switch browser"]
  G --> J["Review campaign dial settings at peak hours"]

If the server summary points to a hardware constraint, the next step is checking your Server Performance Report and system load graphs. The broader context for doing this systematically is covered in our server health and capacity guide.

What to do with recurring lag on the same server

Recurring LAGGED events on one server almost always trace back to one of three root causes: a Keepalive process that has stalled and is consuming threads, a database query that is taking too long under call volume, or an underpowered server running a campaign that its vCPU count cannot support. The Agent LAGGED Report gives you the evidence; fixing it means adjusting the campaign, restarting the offending process, or resizing the box.

For a broader view of when lag events bunched up over a day or week, the LAGGED Summary Report shows the same data as an aggregated timeline chart. That is covered in How to read the LAGGED Summary Report.

If you want a server that is sized right for your call volume from day one, take a look at VICIfast plans and pricing — every managed box ships pre-tuned and live in under 40 seconds.