Configuration is broken for some reason…
We are seeing a persistent 409 Conflict error when attempting to upload a new contact list segment for our outbound campaign via the /api/v2/outbound/campaigns/{campaignId}/lists endpoint. This happens specifically when the upload window overlaps with our weekly WFM schedule publication process. The environment is Genesys Cloud US-East-1, version 2024.5. The error payload indicates a ‘Resource state inconsistent’ issue, suggesting a lock contention between the outbound contact list ingestion service and the workforce management schedule publish job. Both processes are triggered by the same Orchestrator flow at 06:00 AM America/Chicago on Fridays. The outbound team needs the list ready for the morning shift, but the WFM publish seems to be holding a database lock on the shared agent resource tables. We have tried staggering the start times by 15 minutes, but the conflict persists. The contact list contains approximately 15,000 records with custom dispositions mapped to our current adherence rules. Has anyone encountered a similar lock contention issue between Outbound and WFM modules? We need a reliable way to decouple these processes or identify which specific resource is causing the state inconsistency. The Architect flow logs show the WFM publish completing successfully, but the outbound API call fails immediately after. Any insights on how to resolve this race condition would be greatly appreciated.