When i am using Spec URL for my ressouce, retool is completly ignoring my server setting on an app that has been exported from a different retool instance.
I’ve added the production environment after i was finished on the local dev system (using ngrok), but retool is still using the ngrok addresses and not, as configured to prod url:
Here you see my prod retool settings of the ressource:
Workarround so far is, to export the app and replace all the urls in the json file. Which makes no sense to me, especially, why is the api url in the app.json? Wouldn’t it make sense to have only the reference to the ressource there?
this is expected @Tobias_Sell. retool doesn't resolve the base URL from the resource for existing queries. you’d need to define your environments and refresh the resource. you can also recreate the queries
Thanks for reaching out, @Tobias_Sell! You're right that this is a little bit broken right now. I initially figured it was an isolated byproduct of exporting and importing the app between instances, but it highlights a more general gap in the way changes to the resource spec are propagated to queries.
The only consistent, functional workaround I've found is to force a new save of the query via a cosmetic change - toggling the selected endpoint or even adding a dummy query param both seem to work.
I'll reach out to the team and talk through potential solutions!
Its used in a big app, that ressource has more than 50 querys. Its annoying to touch them all. My current workarround is, to simply search and replace in the json-export.
Happy to see it fixed in the future
