We are attempting to implement a disaster recovery strategy by exporting the entire Genesys Cloud organization configuration into Terraform state. The goal is to capture every user, queue, and routing profile in a single terraform import run. We are using a script that queries the /api/v2/users and /api/v2/queues endpoints to generate the import commands. The process works for standalone resources, but it consistently fails when the provider tries to resolve dependencies between users and their assigned routing profiles. The state file shows the resources exist, but the subsequent terraform plan marks every dependent resource for recreation instead of detecting the existing configuration. This suggests the import process is not correctly linking the foreign keys or IDs in the state. We have verified that the OAuth token has the necessary read:user and read:queue scopes. The error message returned is Error: resource not found even though the API returns the resource successfully. Is there a specific flag or provider configuration required to force the import of dependent resources? The documentation mentions a full-export capability, but we cannot find a concrete example of how to invoke it via the CLI or the provider directly. We need a reliable way to snapshot the org without manual intervention. The current approach is too fragile for production use. Any insights on how to handle these dependency chains during import would be appreciated.