The API returns 400 Bad Request with message ‘Invalid queue configuration’ when linking to a queue migrated from Zendesk.
We are in the final stages of migrating our outbound dialing operations from Zendesk Talk to Genesys Cloud, and I have hit a wall with the predictive outbound campaign activation in the EU-West region. The setup involved mapping our Zendesk agent groups to Genesys Cloud business units and creating corresponding queues using the Terraform Provider v1.12.0. The initial resource creation was successful, and the queues appear correctly in the Admin console with the expected skills and agent assignments. However, when attempting to activate a new predictive outbound campaign via the API, the response consistently fails with the 400 error mentioned above.
The specific endpoint being called is POST /api/v2/outbound/campaigns, and the payload includes the campaignId, campaignType set to ‘PREDICTIVE’, and the queueId that was migrated. The error details in the response body point to a validation failure on the queue configuration, specifically mentioning that the queue does not support the required dialing strategy. In Zendesk, we handled outbound calls through a simple tag-based assignment, but in Genesys, I understand that predictive dialing requires specific queue settings, such as a non-zero max concurrent calls value and proper agent availability rules. I have verified that the queue settings in Genesys match the recommended configuration for predictive dialing, including setting the wrap-up time and ensuring agents are properly provisioned with the necessary skills.
The SDK version in use is v3.2.0, and the environment is eu-west-1. I have also checked the Architect flow associated with the campaign, and it seems to be correctly linked to the queue. The issue persists even after deleting and recreating the queue manually through the UI, which suggests that the problem might be related to how the queue metadata is being interpreted during the migration process. Has anyone encountered similar issues when migrating outbound campaigns from Zendesk to Genesys Cloud? Any insights into what specific queue configuration attributes might be missing or incorrectly set would be greatly appreciated. We are under pressure to complete this migration, and this error is blocking our final testing phase.