Running terraform import on an existing Genesys Cloud user returns a 404 error, even though the user ID is correct and accessible via the UI. The command terraform import genesyscloud_user.test_agent 12345678-1234-1234-1234-123456789012 executes without syntax errors, but the state file remains empty for that resource. Debug logs show the provider attempting a GET request to /api/v2/users/12345678-1234-1234-1234-123456789012 and receiving a 404 Not Found response. This happens consistently across multiple resources, including routing queues and skill groups. The API key used has full admin permissions, so it’s not a scope issue. I’ve verified the user exists and is active. No other errors appear in the output, just the immediate failure on import.
Tried invalidating the local state cache and re-running with explicit provider version 1.35.0. Also tested with a different API key generated yesterday. The REST call works fine in Postman using the same token. The Terraform provider seems to strip or modify the request headers, causing the auth check to fail silently. Looking for a way to debug the exact HTTP request the provider sends or a workaround to manually inject the resource into the state file without triggering the import routine.