Fun one today; we’ve got a detail aggregate query that’s suddenly returning incomplete data. It’s pulling call data from the detail-query endpoint - /api/v1/analytics/reports/detail-query - and it’s missing about 30% of the records it pulled yesterday. No changes to the query itself; confirmed that with a diff.
We’re on Genesys Cloud, API version 6.0; Python SDK 3.2.0. The query is pretty standard - filtering by queue ID and a date range. We’ve scheduled this query for years, no hiccups.
Checked the S3 bucket; no errors there. Logs show no exceptions thrown during query execution; it completes successfully - just with less data. Change the date range slightly → the missing records shift; it’s not a static data loss. Something’s up with how the data is indexed or aggregated on the backend, I suspect.
Tried bumping the timeout in the SDK; didn’t help. Re-deploying the worker with the same SDK version, no change. Think they pushed a bad update to the analytics API; maybe a partial index rebuild or something? Anyone else seeing weirdness with detail aggregate queries? Quickest workaround to get the full dataset would be great; I don’t need a postmortem, just a way to get this running again.