Struggling to understand why the Analytics API endpoint /api/v2/analytics/interactions/summary consistently returns a 429 Too Many Requests response when aggregating data for digital channels specifically tagged with legal_hold=true. The environment is Genesys Cloud EU (Frankfurt), and we are using the Python SDK v3.1.2. The request payload includes filters for type: digital_chat, type: sms, and type: webrtc, with a date range covering the last 30 days. The aggregation interval is set to hourly. When the query targets voice interactions, the response time is under 2 seconds, and no rate limiting occurs. However, as soon as digital channel types are included in the filter array, the latency spikes to over 15 seconds, followed immediately by the 429 error. The Retry-After header suggests waiting 60 seconds, but subsequent attempts within that window also fail. We have verified that the API key has the necessary analytics:read and recording:read permissions. The issue persists even when reducing the date range to a single day. The error response body indicates that the request exceeds the allowed quota for complex aggregation queries involving mixed media types. This is critical for our legal discovery workflow, as we need to export metadata for all interaction types associated with specific case IDs. The chain of custody requirements mandate that we capture all digital touchpoints, not just voice. We have tried batching the requests by channel type, but this introduces a risk of inconsistent data if the hold status changes during the export window. Is there a specific limit on the number of digital channel types that can be queried in a single analytics call? Or is this a known limitation with the WebRTC metadata indexing in the EU region? We need a reliable method to aggregate this data without hitting rate limits, as manual scripting is not scalable for our volume of legal holds.