I’m curious as to why the bulk export job is returning script_version_id: null in the manifest.json for conversations routed through dynamic scripts? We are seeing this consistently in our Genesys Cloud environment (EU-1 region) when exporting data for legal discovery requests.
- The export job is triggered via
POST /api/v2/analytics/conversations/exportwith a date range covering the last 48 hours. - The filter includes
conversation.type: voiceandinteraction.media_type: audio. - All exported conversations were handled by agents using a specific Scripting version (ID:
scr_abc123) which was active during the call. - However, the resulting
manifest.jsonfile listsscript_version_idasnullfor approximately 60% of the records. - The S3 bucket receives the audio files correctly, but the metadata link is broken for chain of custody verification.
- We have verified that the IAM policy allows full read access to the Scripting API and Analytics API.
- The issue persists even when using the latest SDK version (v3.1.2) for the export trigger.
- Manual inspection of individual conversations via
GET /api/v2/analytics/conversations/details/{conversationId}shows the correctscript_version_id. - This discrepancy causes significant delays in our legal hold process, as we cannot programmatically verify the compliance of the script used during the call.
- We need to ensure the bulk export metadata aligns with the real-time conversation details for audit trails.
- Is there a known latency issue with the Analytics API syncing script metadata?
- Or is there a specific flag required in the export request body to force script version inclusion?
- Any insights on how to mitigate this mismatch without manual intervention would be greatly appreciated.