My configuration keeps failing…
The bulk export job for recording metadata is failing with a 400 Bad Request error. The request is sent to /api/v2/recordings/bulkexport using Python SDK version 2.180.0. The environment is Genesys Cloud 2024-4 in eu-west-1.
The error response payload shows:
{
"code": "bad_request",
"message": "Invalid date range. Start date must be before end date and within the last 13 months.",
"details": "The filter criteria provided are invalid for the requested operation."
}
The filter configuration is straightforward. We are querying for recordings with a specific legal_hold tag applied during discovery. The start date is 2024-01-01T00:00:00.000Z and the end date is 2024-06-30T23:59:59.999Z. This range is clearly valid and well within the 13-month retention policy.
The metadata schema seems correct. We are requesting media, recording, and participant data. The issue appears when the legal_hold filter is combined with the date range. If the date range is removed, the job runs but returns all recordings, which is not acceptable for discovery compliance.
Is there a known limitation with date filtering on legal hold tags in the bulk export API? Or is the SDK parsing the ISO 8601 dates incorrectly?