Legal Hold Metadata Timestamp Drift in S3 Bulk Export

Looking for advice on a persistent timestamp offset issue during bulk export jobs for legal discovery. The S3 manifest records interaction times that are consistently 15 minutes ahead of the actual Genesys Cloud audit trail.

This drift violates our chain of custody requirements. Is there a specific configuration in the S3 integration or the Recording API that forces UTC alignment rather than local Europe/London time?

You should probably look at at the timezone_normalization flag in your export job configuration. The default behavior often respects the trunk’s registered region, so forcing UTC alignment in the manifest metadata usually resolves this drift.