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?
3 Likes
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.
Heads up on that webhook lock. If you’re stripping signatures or processing HTML in the same flow, it can hang the data action. Make sure your email parsing rules aren’t blocking the outbound trigger. Usually just clearing the cached templates in Architect fixes the stale lock.
2 Likes