How to read the LAGGED Summary Report and spot lag clusters over time

A single lagged event tells you little. A wall of them at 2 p.m. every weekday tells you a lot. The LAGGED Summary Report exists to turn scattered lag records into a picture you can read at a glance — a summary plus a chart of lagged agent events on a timeline over a date range. Its whole job is helping you spot clusters.

Summary first, then the chart

The report opens with a summary of LAGGED agent events across the range you pick, then plots them on a timeline. The summary tells you the volume; the chart tells you the shape. A flat, low line of occasional lag is normal background noise on any busy Agent session. A spike — many lagged events bunched into a narrow window — is a cluster, and clusters almost always have a single cause.

Reading the shape of a cluster

The timeline shape is the diagnostic. Where the cluster sits tells you what to look at:

• Same time every day → a scheduled job, a backup, or a daily peak in call volume hitting the box.
• One-off spike on a single afternoon → a one-time event: a campaign reset, a list load, or a maintenance window.
• Lag climbing steadily through each shift → the server filling up as agents and calls accumulate.
• Random scatter with no shape → likely a network or Keepalive issue, not a load pattern.

From a cluster to a cause

flowchart TD
  A[Open LAGGED Summary chart] --> B{See a cluster?}
  B -->|No, flat line| C[Background noise: no action]
  B -->|Yes| D{Cluster recurs daily?}
  D -->|Yes| E[Find the scheduled job at that time]
  D -->|No| F[One-off: check that day's changes]
  E --> G[Confirm in the detailed LAGGED report]
  F --> G

Why the timeline beats the raw list

If you only ever read individual lagged events, you'd never notice that they all land at the top of the hour, or that they got worse after you bumped a campaign's Predictive dialing pace last Tuesday. The chart makes those patterns obvious. A good habit is to read this summary as a Real-time report companion — when agents complain today, glance at the chart to see if today actually looks different from a normal day, or if it's the same background level they've always had.

Once you've located a cluster on the timeline, switch to the Agent LAGGED Report and filter to that exact window — it names the server IP and lists every agent and Campaign caught in the spike. The two reports are designed to hand off to each other, and both sit inside the VICIdial troubleshooting playbook.

When the pattern points at capacity

A cluster that grows every shift and only clears overnight is the classic shape of a box running near its limit. The lag isn't random — it's the server telling you it's full. Adding headroom flattens the chart. VICIfast runs each dialer on its own dedicated VPS and resizes without taking agents offline, so a busy afternoon stops turning into a lag cluster — see the plans to size for your peak. Read the chart for shape first, confirm in the detail report, and you'll know whether to schedule a job differently or add capacity.