503 error on Query

[mdnperkins]

Hello,

I have a user that's having issues with generating a YTD Queue Performance Report. We've been trying to run a request in the API, but we're getting a 503 error.

Using the /api/v2/analytics/conversations/aggregates/query, this is the payload we're attempting:

{"filter":{"type":"and","clauses":[{"type":"or","predicates":[{"dimension":"queueId","value":"8679bfb7-58d7-456d-a34d-71a16208c1b9"}]},{"type":"or","predicates":[{"dimension":"mediaType","value":"voice"}]}]},"metrics":["nOffered","tAnswered","tAbandon","nOutbound","tFlowOut","nConnected","oServiceLevel","tWait","tHandle","tTalkComplete","tHeldComplete","tAcw","tDialing","tContacting","nTransferred","nBlindTransferred","nConsult","nConsultTransferred","oExternalMediaCount","oMediaCount","nOverSla","tShortAbandon","nOutboundAttempted","tVoicemail","nError","tParkComplete"],"groupBy":["queueId"],"interval":"2024-01-02T06:00:00.000Z/2024-09-17T06:00:00.000Z"}

What are the resource limits for this?

Is there a better way to generate a YTD report for a queue?

[Eos_Rios]

Aggregates are limited by the number of rows your grouping would result in.

Those limits are the whole reason for the new asynchronous endpoint

Today anyone doing that size of a pull is doing it from their own data that they've pulled incrementally through the year, or through scripts that break the request into smaller tailored chunks they've confirmed work and reassembling in their script.