How should I properly to handle missing timestamps in bulk digital export?
We are running a scheduled bulk export job for WhatsApp and Web Chat recordings to meet a legal discovery deadline. The environment is Genesys Cloud EU-West. The export job completes successfully, but the resulting JSON manifests in our S3 bucket show null values for the created_timestamp field on approximately 15% of the records.
This breaks our chain of custody validation scripts, which require ISO 8601 formatted timestamps to verify the recording integrity. We are using the standard /api/v2/recordings/export endpoint. The API documentation states that created_timestamp is always populated for completed sessions.
Is this a known issue with specific digital channels having delayed metadata propagation? Or do we need to implement a retry logic in our data action to wait for the metadata to sync before the export job finalizes?
We cannot proceed with the legal hold transfer until the metadata is complete. Any insight into whether this is a platform bug or a configuration error in our bulk export settings would be appreciated. We have verified that the recordings themselves are intact and playable.