Bulk Export Metadata Mismatch for Bot Interactions

Architect & Flows
1

Anyone know why the interaction_id in the S3 manifest differs from the bot conversation log? We are exporting digital channel recordings for legal discovery. The bulk export job succeeds, but the chain of custody metadata shows a timestamp drift of 120ms. This breaks our audit trail validation.

{
 "exportType": "LEGAL_HOLD",
 "filters": {
 "channel": "WEB_CHAT",
 "botId": "bot_123"
 }
}

Any ideas on forcing strict ISO 8601 alignment?

2

You need to verify the timezone handling in your export configuration.

Cause: The platform processes UTC timestamps against local timezone settings, creating the observed offset.
Solution: Adjust the timestamp handling in the bulk export job to enforce strict ISO 8601 alignment.