is it possible to retrieve screen recording metadata for interactions that originate on specific byoc trunks when the agent desktop is in a different region than the trunk edge? we are running into a consistent 400 bad request when querying the /api/v2/analytics/screen-recordings endpoint for sessions involving our ap-southeast-1 byoc trunks. the agents are logged in via the us-east-1 region, and while the voice stream routes correctly through the failover logic, the screen recording service seems to lose the correlation id.
the error payload returns “invalid_interaction_id” even though we are passing the exact interaction id from the outbound call log. we have verified that the screen recording feature is enabled in the organization settings and that the agents have the necessary permissions. the issue appears to be isolated to sessions where the sip registration is handled by the byoc edge connector in singapore, but the agent workstation is in the us. when we force the trunk to route through a local edge in us-east-1, the recordings are generated and retrievable without issue.
we are using the platform api v2 and have tested this across multiple sdk versions. the latency between the region switch and the recording start time is approximately 400ms, which might be causing the metadata sync to fail. has anyone encountered similar issues with cross-region byoc trunks and screen recording aggregation? we are considering adding a custom attribute to the interaction to flag these cross-region calls, but we would prefer a native solution. any insights on how the recording service handles region boundaries for byoc traffic would be appreciated.