It’s throwing a 400 campaign_schedule_conflict error on POST /api/v2/outbound/campaigns/{id}/start.
{
"error": "campaign_schedule_conflict",
"message": "Campaign hours overlap with protected WFM schedule blocks for 12 agents."
}
Campaign is set to ET business hours. WFM schedule blocks are also ET. Overlap detection is firing even though the schedule object uses strict ISO 8601 formatting.
"schedule": {
"timezone": "America/New_York",
"blocks": [
{"start": "2024-05-15T08:00:00-04:00", "end": "2024-05-15T17:00:00-04:00", "days": ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"]}
]
}
Switched to application/json and verified the timezone field matches. Progress still rejects the payload. WEM adherence dashboard shows those agents as available during that window, but the outbound engine flags it as a protected block. Doing jack all with the rule builder right now. It just sits there.
Running Genesys Cloud 2024-04.14.0. The overlap validation doesn’t seem to read the status mapping in the WFM calendar. Payload structure looks fine. No idea why the engine keeps blocking the push.