How do I correctly to handle genesyscloud_wfm_schedule imports when the shift pattern contains overlapping break rules defined in the genesyscloud_wfm_schedule_patterns resource?
We are deploying WFM configurations via Terraform provider v1.102.0. The schedule import fails with a 400 Bad Request during the genesyscloud_wfm_schedule creation step. The error payload indicates a conflict in break rule application for the specific date range.
resource "genesyscloud_wfm_schedule" "agent_schedule" {
name = "Agent Shift A"
schedule_type = "SHIFT_PATTERN"
schedule_patterns {
pattern_id = genesyscloud_wfm_schedule_patterns.main_pattern.id
start_date = "2024-01-01"
end_date = "2024-12-31"
}
}
The API response suggests the break rules are not being resolved correctly against the shift duration.
“Schedule patterns must not contain overlapping break definitions that exceed the total shift duration. Ensure break rules are mutually exclusive within the pattern definition.”
Is there a specific sequence required for applying schedule patterns before importing schedules? The documentation is vague on dependency ordering for complex shift patterns. The GC CLI import also fails with the same validation error. We are in the Sydney timezone, but the schedule is set for UTC. Does the timezone offset affect the validation logic during import?