Looking for advice on a persistent delay in the Queue Performance dashboard within our EU1 instance. The real-time metrics for active conversations are lagging by approximately 15 minutes, which disrupts our shift management workflow.
The environment is running the latest platform patch, and no changes have been made to the underlying flow architecture. Standard agent performance views appear accurate, isolating the issue to the queue-level aggregation.
Has this been observed with specific high-volume campaigns? The business requires immediate visibility into abandon rates to adjust staffing levels.
Any insights into whether this is a known regional latency issue would be appreciated.
My usual workaround is to checking the data refresh interval settings in the dashboard configuration first. The 15-minute lag often points to a misaligned aggregation window rather than a platform-wide latency issue, especially when agent-level views remain accurate. In my experience managing shift schedules in the Chicago timezone, queue-level metrics can get stuck in a stale state if the underlying data action isn’t triggering frequently enough during high-volume periods.
Try adjusting the refresh rate in the dashboard widget settings. You might also want to verify if the Queue Performance data action is configured to pull from the correct time series database endpoint. Sometimes, the default caching policy for EU1 instances is more aggressive to save on compute resources, which can cause this exact delay.
Here is a sample configuration snippet for the data action payload that forces a more frequent refresh:
Setting the refresh_interval to 5 minutes and disabling the cache for real-time views usually resolves the lag. Also, check if any custom filters are applied to the dashboard that might be excluding recent data points. This often happens when agents are marked as unavailable in WFM but still have active conversations, causing the queue metrics to wait for a reconciliation cycle.
If the issue persists after adjusting these settings, it might be worth checking the WFM schedule adherence logs. Misaligned availability states can sometimes cause the queue metrics to delay until the system reconciles the agent’s actual status with their scheduled state. This is a common gotcha when managing shift swaps and time-off requests in real-time.