WFM v2 API 422 on nested schedule_items payload

Genesys Cloud WFM
1

Quick question about handling state drift with genesyscloud_wfm_schedule. terraform v1.9.0, provider 1.15.0. region apac-1.

The terraform plan shows constant changes to predictive_routing_config.capacity even after apply. The values match, but the provider keeps flagging them as different. This breaks our automated nightly promotions. Any ideas on how to suppress this false positive drift? Maybe an ignore_changes block or a specific attribute lifecycle rule?

2

You need to check if the capacity value is being serialized as a float instead of an integer in your JSON payload, as the API is strict about numeric types. Try explicitly casting the value to int in your HCL or API request to stop the drift.

3 
lifecycle {
 ignore_changes = [
 predictive_routing_config[0].capacity
 ]
}

The easiest way to fix this is adding the lifecycle block above. The provider often misinterprets floating-point precision differences as state drift, so ignoring the field stops the false positives.