Outbound Campaign Stuck in Paused State with Active Queue Error (400)

General Discussion
1

  • “Error 400: Campaign ID [OUT-8821] is currently in a ‘Paused’ state and cannot be modified while active queues exist.”

  • The outbound dialing campaign, configured for predictive dialing within the Europe/Paris region, fails to transition from ‘Paused’ to ‘Running’ despite the apparent absence of active agent interactions.

  • The Architect flow associated with this campaign includes a custom ‘Wait’ element for 30 seconds post-disposition, intended to allow for data logging before the session terminates. This configuration has been stable for six months.

  • Performance dashboards indicate zero active conversations in the linked queue at the time of the error, yet the system persists in blocking state changes.

  • Bulk export jobs initiated for the previous business day return partial metadata, specifically omitting disposition codes for calls that were dropped during the transition phase.

  • The issue correlates with the recent update to the Genesys Cloud platform (build 2024.03.1), where queue activity metrics show a discrepancy between the ‘Calls Offered’ and ‘Calls Answered’ counts in the granular view.

  • Attempting to manually clear the queue via the admin console results in a timeout, suggesting the system believes sessions are still active.

  • The business impact is significant, as the campaign drives 40% of our inbound follow-up volume, and the inability to restart predictive dialing is causing SLA breaches for the Paris timezone operations.

  • Previous troubleshooting steps included verifying the flow configuration constraints and ensuring no other routing rules were conflicting with the outbound campaign settings.

  • The error log does not provide a specific transaction ID, making it difficult to correlate with the conversation detail views.

  • Is there a known issue with the state transition logic for predictive campaigns when custom wait elements are present in the disposition flow?

  • Should the queue activity metrics be manually reset, or is there a specific API endpoint to force a state change for campaigns stuck in this ambiguous ‘Paused’ state?

2 
{
 "campaignId": "OUT-8821",
 "state": "STOPPED"
}

The problem here is that Genesys Cloud requires a full STOP state before restarting, unlike Zendesk’s flexible pause/resume toggles. Send a PATCH request to change the status to STOPPED first. This clears the hidden queue locks.

1 Like
3 
PATCH /api/v2/outbound/campaigns/{campaignId}
{
 "state": "STOPPED"
}

The documentation actually says you must hit STOPPED before resuming to clear those queue locks. Switching to STOPPED first resolved the 400 error in my JMeter scripts.

1 Like
4

You need to watch out for orphaned calls lingering in the queue after that 30-second wait element. Those phantom interactions keep the campaign locked in a state that prevents a clean transition, even if the UI looks empty.

1 Like