just noticed that the /api/v2/analytics/conversations/details endpoint starts throwing 503 errors when we hit 50 concurrent requests from jmeter. its happening in the ap-southeast-1 cluster and the rate limit headers seem fine but the response time spikes to 10s before failing. anyone seen this with the platform api?