Could use a hand troubleshooting this persistent 422 Unprocessable Entity error during WFM schedule imports. Environment is ap-southeast-1. Using Terraform v1.7.5 and provider v1.12.0. The pipeline fails at genesyscloud_wfm_user_schedule. Payload validates locally but rejects on apply. See config below.
resource "genesyscloud_wfm_user_schedule" "shift" {
name = "Shift-A"
type = "shift"
start_time = "08:00"
end_time = "17:00"
}
Any known schema mismatches?
resource “genesyscloud_wfm_user_schedule” “shift” {
name = “Shift-A”
type = “shift”
start_time = “08:00”
end_time = “17:00”
user_id = “your-user-id” # Mandatory for shifts
}
This is caused by a missing `user_id` attribute. Unlike Zendesk’s abstract assignment rules, Genesys Cloud WFM requires explicit user binding for individual schedules. The 422 error confirms the server rejects the payload without this identifier. Always verify field requirements against the API docs!
I normally fix this by adding the user_id as As noted above, but watch out for time zone mismatches in the start/end times. The API expects UTC, so “08:00” might not align with your local CST or ap-southeast-1 business hours without conversion.
Check your user mapping in the Architect flow if this schedule drives routing. The Terraform fix is correct, but ensure the underlying user data aligns with queue requirements. A 422 error here often masks a broader data integrity issue in the WFM module.