When converting or creating a new app with the new Beta app builder, it can’t detect my BigQuery resource. It is not private and sits in the same folder as my other resources. The app can detect my other resources, but it doesn’t detect BigQuery. Is anyone else seeing this, or know of a solution?
Summary
Using the new (Beta) app builder to convert or create an app, an existing, non-private BigQuery resource isn't detected/surfaced to the app, even though it sits in the same folder as other resources that are detected.
AI Response
This matches a known class of new app builder behavior where existing workspace resources intermittently fail to surface to the app and its chat agent. The typical remedies confirmed by Retool staff are to hard-refresh the app page and, if that doesn't work, start a brand-new chat thread so the sandbox re-scans available resources. Retool has also shipped sandbox changes that significantly improved resource discovery, so ensure the instance is on a current version and confirm the BigQuery resource is shared to the same workspace. If it still won't appear after refreshing and starting a new thread, it aligns with reports where discovery of a specific resource lags behind others.
Sources
App won't surface an existing Google OAuth 2.0 REST resource
Solved new-app-builder report of an existing resource not surfacing to the app/agent; Retool staff confirmed the bug and gave a workaround (page refresh, then start a new chat thread) plus noted sandbox improvements to resource discovery.
A parallel new-app-builder report where an existing resource (Google Drive) was not detected despite hard refreshes, corroborating the same detection issue seen with the BigQuery resource.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 