Outbound Campaign 400 Error on Predictive Dialing Configuration

General Discussion
1

Having some config trouble here as expected within the Genesys Cloud Outbound module. We are attempting to launch a new predictive dialing campaign for the Paris region, targeting a specific list of contacts. The flow architecture has been validated and is active, yet the campaign fails to transition from the ‘Draft’ state to ‘Running’. Upon saving the configuration, the system returns an HTTP 400 Bad Request error with the message: “Invalid campaign configuration: predictive rate exceeds maximum allowed threshold for region.”

The environment details are as follows: Genesys Cloud version 2024-Q2, operating within the eu1 region. The predictive rate is configured at 1.5, which should be well within standard limits for our license tier. Queue activity metrics indicate zero load, and agent availability is confirmed. The issue appears isolated to the campaign definition rather than the underlying flow logic, as manual outbound calls via the same flow succeed without interruption.

Could the discrepancy stem from a mismatch between the defined predictive rate and the regional compliance settings enforced by the platform? We require clarification on the specific business rules governing predictive rate limits in the eu1 region to adjust our configuration accordingly. Any insight into resolving this 400 error would be appreciated.

2

Invalid campaign configuration: predictive rate exceeds maximum al

This is caused by the predictive rate exceeding the maximum allowed for your current license tier or agent capacity. Check the outbound campaign settings and reduce the predictive rate to match your available workforce.

3

I think the predictive rate limit is strictly enforced to maintain compliance. Adjusting the JSON payload usually resolves the 400 error. Here is a standard configuration structure:

{
 "predictive_rate": 1.2,
 "max_concurrent_calls": 50
}