Trying to make sense of why the genesyscloud_script resource is consistently showing state drift during our GitHub Actions promotion pipeline from Dev to QA. The local state file matches the remote state, yet the plan phase reports a change in the flow_version attribute every time.

Environment details:

• Provider: genesyscloud v1.18.4
• Terraform: v1.6.4
• Target: Genesys Cloud (US East)
• Source Control: GitHub Actions

Steps to reproduce:

1. Define a basic script resource in HCL with a single text block and standard properties.
2. Run terraform apply in the Dev environment. The script is created successfully.
3. Commit the state file and HCL to the repository.
4. Trigger the promotion workflow to QA. The workflow pulls the Dev state, updates the provider configuration for the QA org, and runs terraform plan.
5. The plan output shows a diff on the flow_version field, indicating it wants to update the script despite no changes in the source code.

The specific error message in the plan output is:
`

module.reporting.genesyscloud_script.agent_onboarding

will be updated in-place
~ resource “genesyscloud_script” “agent_onboarding” {
~ flow_version = “2023-10-27T05:00:00Z” → “2023-10-27T05:00:01Z”

(15 unchanged attributes hidden)

}
`

This causes the pipeline to fail our plan-only check that requires zero changes for promotions of identical configurations. We are using the genesyscloud_script resource to manage agent scripting for compliance purposes. The drift seems to occur even when the script content is identical in both environments. We have tried using lifecycle { ignore_changes = [flow_version] }, but this suppresses the warning and risks missing actual content changes. Is this a known issue with the provider version or is there a specific way to pin the version hash in the HCL definition? Need a solution that allows automated promotion without manual intervention.