Summary
In the New App Builder, two previously working Azure OpenAI resources called via
.text.generate()from a backend function now return '404 Resource not found' — thrown inside /sandbox/jse-libraries/resource-query.js before the request reaches the provider — even though the resources are listed as granted in the app's manifest, still work in classic Retool apps, and key rotation made no difference.AI Response
This pattern matches a known issue where the New App Builder's sandbox fails to fetch up-to-date resource definitions, so a resource that is granted (and works in classic apps) isn't resolved at the backend/function layer and errors out before reaching the provider. Retool staff have confirmed this sandbox resource-resolution behavior and the most reliable workaround is to force a re-sync: open a brand-new chat thread (and hard-refresh the builder), or simply wait ~10 minutes for the sandbox to re-scan available resources. Also confirm the resources are in the same workspace and shared with a group where you hold Edit or Own access, since the agent only connects resources at that access level, and try explicitly @-tagging each Azure OpenAI resource by name so it is re-attached.
Sources
Custom REST resource not visible to new App Builder backend
A near-identical case where an OpenAI-related resource is granted but unreachable by New App Builder backend functions; Retool staff confirmed the sandbox wasn't fetching current resource definitions and gave the direct workaround of opening a new thread or waiting ~10 minutes to force a sync.
The official guide on connecting resources and functions in new apps, confirming the agent only connects resources you have Edit or Own access to and that you can @-tag a resource by name to have it reconnected.
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. 