Dealing with a very strange bug here with the Analytics API when attempting to retrieve metadata for completed bulk export jobs specifically tagged for legal discovery. The environment is Genesys Cloud 2024-02 in the EU1 region. We are using the genesyscloud-node-sdk v2.1.0 for our automation scripts.
The issue occurs when calling POST /api/v2/analytics/details/query. The goal is to pull detailed audit trails for digital channel transcripts (Webchat/Social) that have been exported to our S3 bucket under a legal hold policy. The export jobs themselves complete successfully with status completed, and the S3 integration logs show correct permissions. However, when the analytics query attempts to join the export job metadata with the conversation data, the response returns a 400 Bad Request.
The specific error message in the response body is: "The filter 'export_job_id' is not supported for this metric set." This is confusing because the documentation for the conversation metric set implies that export-related fields should be accessible for legal hold reporting. We have verified that the export_job_id exists in the raw JSON of the exported files, so the data is present.
Here is the simplified payload structure causing the failure:
{
"metric_names": ["duration", "export_status"],
"group_by": ["conversation_id"],
"filter": {
"type": "and",
"clauses": [
{
"type": "eq",
"field": "export_job_id",
"value": "job-xyz-123"
}
]
}
}
We need this data to reconstruct the chain of custody for a specific case. Is there a workaround to link export jobs to conversation analytics, or is this a known limitation in the 2024-02 release? We cannot manually cross-reference thousands of records. Any insights on correct filtering syntax or alternative endpoints would be appreciated.