Hello Tonya! This is the way the view was designed. The paging of the view will load 50 agents and then load the metrics for each agent. If it had to populate the summary row for results past 50, it would need to query the metrics for each one of those agents. The total amount of queries that page would need to run would be equal to the amount of total agents based on the filter you have applied. Populating that row when total agent counts can be into the thousands would generate too many API requests on page load.
When exporting this data, the export will query the metrics for each agent. A UI needs to load all its data within a couple seconds otherwise we'd leave the user watching a loading icon endlessly. An export can afford the time to gather those metrics together and populate the summary row when the total agent count is many pages deep.
------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------