Summary: We will reduce the maximum page size for the GET /routing/queues/{queueId}/users endpoint from 500 to 100. This is to improve system resilience, due to the load that a request with a large page size combined with certain parameters can have on the system.
Impact: Callers may see fewer items per response page than previously. All data is still available, but may be spread across more pages.
the endpoint will just return up to 100 items. it will not throw an error if the requested page size is over 100. (we want this change to be largely non-breaking.)
To add to this, this is the existing behavior for this API today but it enforces a cap of 500 if you request something larger. The change is only to lower that cap; the behavior of the API remains unchanged. You'll only be impacted by this if you have something hardcoded to access more than 100 elements from the response instead of counting the items in the result set. If you're dynamically processing the results based on the length of the collection, you shouldn't have to make any changes, even if you're still requesting 500 items per page.