Bulk Export 400 on Agent Scripting Metadata Filter for Legal Discovery

Anyone know why the bulk export job fails immediately with a 400 Bad Request when attempting to filter by agent scripting metadata for digital channel interactions? The requirement is to export all chat and callback interactions where specific script nodes were triggered, specifically for a legal discovery request requiring a complete chain of custody for compliance audit trails.

environment: genesys cloud byoc eu-west-1.
endpoint: post /api/v2/bulkexports/exportjobs.
filter: interaction_type equals digital, scripting_node_id equals ‘compliance_disclosure_v2’.

the api returns 400 with message: “Invalid filter criteria: scripting_node_id is not a supported filter for bulk export jobs on digital channels.”

we have verified that the scripting_node_id exists in the interaction details via the get /api/v2/interactions/interactions endpoint. the metadata is present in the response body under interaction.scripting.nodes. however, the bulk export job creation endpoint rejects this filter.

according to Genesys Docs, scripting metadata should be available for filtering in bulk exports for compliance purposes. is there a specific configuration or data action required to enable scripting metadata filters for bulk exports? or is this a known limitation in the eu-west-1 byoc environment?

we have also tried using the interaction_type equals digital filter alone, which succeeds, but the resulting dataset lacks the scripting node details needed for legal hold verification. the export job completes, but the csv files do not include the scripting_node_id column.

this is critical for our legal discovery process. we need to ensure that all interactions with specific compliance script nodes are exported with their metadata intact. any guidance on how to resolve this 400 error or alternative methods to extract scripting metadata for digital channels in bulk would be appreciated.

we are using the latest version of the genesys cloud api client library. the issue persists across multiple test accounts in the eu-west-1 region. please advise on the correct approach to filter by scripting metadata in bulk exports for legal compliance.