Could someone explain why our custom Data Action is failing with a 400 Bad Request when attempting to sync call metadata from ap-southeast-1 BYOC trunks? The integration was working fine last week, but now the Genesys Cloud API returns a validation error on the external_call_id field. We are using v2.0 of the Data Action SDK and the Architect flow triggers the action on Call Started. The payload includes standard SIP headers and carrier-specific routing info. The error message indicates that the external_call_id format is invalid, but we are passing the exact same format that worked previously. Is there a recent change in the validation logic for BYOC trunk metadata? We have 15 trunks configured with specific failover logic, and this issue is affecting all of them. The SIP registration status is stable, so the problem seems to be isolated to the data sync process. Any insights on the expected format or recent API changes would be appreciated. We need to resolve this quickly as it impacts our reporting accuracy.