Could someone explain why bulk export jobs for AI bot interactions are omitting legal_hold metadata?
Background
Genesys Cloud v2024.02. Exporting digital channel transcripts via S3 integration for discovery requests.
Issue
Standard voice exports include legal_hold=true in the JSON payload. Bot interactions return the same schema but the field is always false, despite the legal hold being active on the account.
Troubleshooting
Verified via API that the hold is applied. Checked Architect flow; no custom attributes are overriding the flag. Is this a known limitation for bot channels?