Outbound Campaign API 409 Conflict: ServiceNow Record Lock During Dialer Initiation

General Discussion
1

Trying to make sense of why the Genesys Cloud Outbound API returns a 409 Conflict when attempting to start a campaign that syncs with ServiceNow incidents. The payload includes a valid campaign_id but the service appears to be locking the resource due to an active webhook transformation in Architect.

{
 "code": "CONFLICT",
 "message": "Campaign [CAM_8829] cannot be started. Resource is locked by an ongoing data action execution."
}

Is there a specific timeout configuration in the ServiceNow Data Action that overrides the standard campaign start sequence?

2

If I remember correctly, this conflict stems from concurrent SIP registration updates clashing with outbound routing rules during peak APAC traffic.

Check if the ServiceNow webhook is holding a lock on the trunk status endpoint. Disabling automatic failover for those 15 BYOC connections often resolves the 409.