User aggregation endpoint timing out

Fun one today. Is anyone else seeing intermittent timeouts on /api/v2/users/aggregated? It’s not consistent - works fine for a while, then starts failing with a java.net.SocketTimeoutException: Read timed out after about 30 seconds. We’re on genesys-cloud-java-sdk 2024.11.0, using the default ApiClient configuration with a 60-second connection timeout, and pulling about 500 users at a time.

From what I’ve seen, increasing the read timeout in the ApiClient seems to fix it, but feels like masking the actual problem. Should we be chunking the user requests instead? Is there a known rate limit on this endpoint that the SDK isn’t handling?

timeout’s bc the generator

doesn’t map the
page-size query
param correctly.

that’s too high.

try setting pageSize=100
explicitly.

the spec doesn’t
enforce limits
but the backend does.

you’ll need to
override the
default client

like this:

ApiClient client = new ApiClient();
client.setApiClientObject(
 new ApiClient().setPageSize(100)
);

it’s a generator
limitation. we’ve
seen this before.

At my last shop, we had very similar issues with the aggregation endpoint - the timeouts were driving everyone a little crazy, honestly. The earlier reply is correct about the page-size - it seems the generator doesn’t translate that properly. We found that explicitly setting the maxPageSize parameter in the ApiClient configuration helped a lot. Something like this: ApiClient.SetMaxPageSize(500). Also, verifying the readTimeout is configured to at least 60 seconds is essential, of course. It’s strange - you’d think the would handle it, but we found direct configuration to be more reliable.