We are working on bringing our legacy Genesys Cloud configuration under strict IaC control. The plan is to use terraform import for existing resources rather than a full migration. Most simple objects like users or queues import without issue. The problem arises with the genesyscloud_routing_strategy resource.
I have generated the import ID using the API call GET /api/v2/routing/strategies to get the UUID. The command looks like this:
terraform import genesyscloud_routing_strategy.my_strategy <uuid-from-api>
The import fails immediately with a 409 Conflict. The error message in the logs states: Error importing resource: Conflict. Resource already exists or ID mismatch. This is confusing because the state file is empty for this resource. I have verified the ID multiple times. I suspect the provider is checking for some internal dependency or a naming convention that isn’t obvious. Has anyone successfully imported complex routing strategies? The documentation mentions state drift, but this feels like a blocker before we even start managing the resource. We need a way to force the import or understand what prerequisite is missing.