We are currently debugging a persistent 409 Conflict error when attempting to create outbound campaigns via the Platform API (/api/v2/outbound/campaigns) within our AppFoundry partner application. Our solution manages dialing operations across multiple Genesys Cloud organizations using multi-tenant OAuth flows.
The specific scenario involves creating a campaign with a defined list source and disposition codes. While the initial campaign creation succeeds in approximately 70% of requests, the remaining 30% return a 409 status code with the message ‘Conflict: Campaign with the same name already exists.’ This occurs despite our implementation of unique naming conventions incorporating tenant IDs and timestamps to ensure uniqueness across the multi-tenant environment.
Environment Details:
- API Version: v2
- SDK: Genesys Cloud Node.js SDK v5.2.1
- Integration Type: AppFoundry Partner App with Multi-Org OAuth
- Endpoint: POST /api/v2/outbound/campaigns
We have verified that no duplicate campaigns exist in the target organization prior to the API call by querying the campaign list endpoint. Additionally, we have implemented exponential backoff strategies for retry logic, but the conflict persists even after waiting periods. The issue appears to be intermittent and does not correlate with specific API rate limits, as our request volume remains well below the documented thresholds.
Has anyone encountered similar 409 Conflict errors during outbound campaign creation in a multi-tenant context? We suspect there may be a race condition or a caching layer issue within the Genesys Cloud backend that is not respecting our unique naming constraints. Any insights into potential workarounds or API behaviors we might be missing would be greatly appreciated.