Why does this setting fail to serialize deeply nested variables when using includeMetadata=true on the Recording API? We are currently managing 15 BYOC trunks across APAC regions, and the failover logic seems to trigger intermittently during peak hours. This creates a scenario where the SIP registration state fluctuates, causing the architect flow to drop specific metadata tags before the recording is finalized.
The issue manifests specifically when agents utilize complex scripting flows that involve dynamic variable assignment based on carrier-specific quirks. When we attempt to bulk export these recordings for legal discovery, the JSON payload returned by the API lacks the expected script execution history. The error is not immediate but appears during the post-processing phase, where the batch job returns a 403 Forbidden status due to token refresh mismatches with the batch processing window.
We have verified that the outbound routing rules are correct and that the SIP credentials are valid. However, the underlying flow architecture does not seem to support the serialization of these nested objects. The Recording API documentation suggests that includeMetadata should capture all context, yet in practice, it omits critical path details. This gap complicates our compliance audits, as we cannot trace the exact script path taken by the agent during the call.
Has anyone encountered similar issues with metadata serialization in Genesys Cloud? We are looking for a workaround that does not involve refactoring the entire architect flow. Any insights on how to force the API to include these nested variables would be appreciated. We need a reliable method to ensure that all script metadata is captured accurately for our reporting needs.