Trying to understand the specific validation logic triggering a 409 Conflict when provisioning SIP trunks via the Platform API within our multi-tenant AppFoundry integration.
Context:
Our application manages telephony infrastructure for over fifty distinct Genesys Cloud organizations. We utilize the PUT /api/v2/telephony/providers/edges/sip/trunks endpoint to synchronize trunk configurations based on customer-specific requirements. The integration handles authentication via OAuth 2.0 client credentials, rotating tokens per organization context.
Recently, deployments for three specific tenants have begun failing with a 409 Conflict status code. The error payload indicates a duplicate resource conflict, specifically citing the trunk name or the associated edge ID. However, our pre-flight checks query the GET /api/v2/telephony/providers/edges/sip/trunks endpoint for each target organization, confirming that no trunk with the intended name exists prior to the creation attempt. Furthermore, we are not reusing edge IDs across different organizations, as each tenant operates within its own isolated OrgId namespace. The issue appears intermittent, affecting only certain API regions or specific time windows, which suggests potential eventual consistency delays in the directory service or a race condition in our batch processing logic. We are using the latest version of the Genesys Cloud Java SDK (v1.58.0) and have implemented exponential backoff with jitter for retry logic, but the conflict persists after multiple retries.
Question:
Does the Genesys Cloud platform enforce a global uniqueness constraint on SIP trunk names across all organizations, or is this strictly scoped to the individual OrgId? If the latter, what mechanisms might cause a 409 Conflict when the local query confirms the resource does not exist? Are there known issues with the directory propagation delay that could result in false-positive conflict errors during rapid sequential provisioning? Any insights into the internal validation sequence for trunk creation would be greatly appreciated.