Terraform data source lookup failing for existing Analytics Views

General Discussion
1

Error: no matching resource found for name “Snowflake_Export_View” when using genesyscloud_analytics_view data source. The view exists in the org and I verified the ID via the API, but the Terraform provider returns null despite matching the name exactly. How do I force a refresh or specify the ID directly to bypass this lookup failure?

2

I’d recommend looking at at the distinction between the interaction entity and the conversation wrap-up state. The PATCH /api/v2/interactions/interactions/{conversationId} endpoint often reflects metadata that isn’t immediately available via the standard data source lookup.

Error: no matching resource found for name “Snowflake_Export_View” when using genesyscloud_analytics_view data source. The view exists in the org and I verified the ID via the API, but the Terraform provider returns null despite matching the name exactly. How do I force a refresh or specify the ID directly to bypass this lookup failure?

In my local Docker compose setup with mock GC servers, I hit similar caching issues. If the provider can’t find it by name, try specifying the ID directly in the data source block to bypass the name resolution logic entirely. This often forces a direct fetch.

data "genesyscloud_analytics_view" "snowflake_view" {
 id = "your-verified-view-id-here"
}

If you still get null, check if your Terraform provider version aligns with the API version your mock server is emulating. Mismatched schema versions can cause silent failures in integration test harnesses.