Running into race conditions with the Java SDK when firing off 500 parallel user updates. The default OkHttpClient instance seems to be shared across threads, causing connection pool exhaustion after about 200 requests.
Is there a documented way to inject a custom, thread-safe OkHttpClient with a higher maxIdleConnections into the ApiClient? I’m seeing 502 Bad Gateway errors and the SDK logs aren’t helping much here.