resource "genesyscloud_wfm_schedule_group" "shift_planner_eu1" {
name = "Berlin Shift Planner - Tier 2"
description = "Automated schedule generation for Tier 2 support"
division_id = var.support_division_id
settings {
schedule_type = "weekly"
timezone = "Europe/Berlin"
wrap_up_codes = ["2001", "2005"]
}
}
Executing the deployment via GitHub Actions on ubuntu-latest. Terraform 1.7.4 paired with provider 2.18.0. The apply sequence halts at the WFM resource and drops a 422. The debug output just mentions a constraint violation in the schedule engine. It doesn’t specify which field is breaking the validation.
{
"error_code": "422",
"message": "Invalid configuration for schedule group. Constraint violation in schedule engine.",
"status": "UNPROCESSABLE_ENTITY",
"trace_id": "7f3a9c21-44b2-9e8f-a1c0-000000000001"
}
The CLI genesys cloud wfm schedule-groups list --name "Berlin Shift Planner" returns empty. Tried forcing a refresh with the CLI but the token expires before the job finishes. The forecast model is already linked to the correct queue, so the workforce routing policy shouldn’t be blocking it. Maybe the timezone offset is throwing off the shift boundaries. Console shows nothing. The pipeline won’t proceed past step 4.
- name: Deploy WFM Resources
run: |
tf apply -auto-approve -var-file="env/eu1.tfvars"
env:
GENESYS_CLOUD_REGION: eu-1
TF_LOG: DEBUG
The 422 recurs on each execution. Don’t know if the provider is sending the wrong payload structure for the schedule settings or if the adherence rules are conflicting with the forecast engine. The documentation just says to check the division hierarchy.