I’m trying to use the genesyscloud provider to export our entire org config for a DR drill. We’re running the standard terraform import loop based on the docs, but it keeps choking on the routing strategies. The error is pretty specific: “Error importing object: Error importing resource: 1 error occurred: * Error reading RoutingStrategy: 400 Bad Request…”. It looks like the API is throwing a fit because some of our strategies reference queues that haven’t been imported yet, or maybe there’s a circular dependency I’m not seeing. The export script runs fine for users and integrations, but the moment it hits the routing section, it bails out. Here’s the snippet from the logs:
module.routing.genesyscloud_routing_strategy.my_strategy: Importing from ID "abc-123-def"...
module.routing.genesyscloud_routing_strategy.my_strategy: Import prepared!
module.routing.genesyscloud_routing_strategy.my_strategy: Refreshing state... [id=abc-123-def]
╷
│ Error: Error reading RoutingStrategy: 400 Bad Request
│
│ with module.routing.genesyscloud_routing_strategy.my_strategy,
│ on routing.tf line 12, in resource "genesyscloud_routing_strategy" "my_strategy":
│ 12: resource "genesyscloud_routing_strategy" "my_strategy" {
The JSON payload in the error body says "errors": [{"message": "Invalid configuration: Queue reference not found"}]. I’ve tried importing the queues first, then the strategies, but the order seems to matter less than I thought. Is there a way to disable the validation during import, or do I need to manually fix the dependency graph in the state file before running the import? We’ve got about 50 strategies and I’d rather not script a custom dependency resolver if there’s a flag I’m missing.