New env on GQL resource, test auth workflow using wrong env

💬 App Building
, ,
1

1) My goal: Run auth test workflow on a newly added env to a GQL resource
2) Issue: I have added a new env (duplicated an existing one) to our GQL resource, changed various configurations (base url, some keys, etc).

But I am unable to use the env in an app until I have tested the auth flow, and I am unable to test the auth flow, because it uses prod env variables instead of the new env variables.
3) Steps I've taken to troubleshoot:

  1. When I go into an app in edit mode, I can see the new env but it is disabled. There is meant to be a tooltip to show WHY it's disabled as explained on your forum here, so it seems there is an issue with Retool itself here

image
image360×153 8.51 KB

  1. In the env settings, when I hit test auth workflow it will go through the correct steps, but seems to take me back to the prod environment, as well as showing the auth attempt in the console + request data, shows me the prod URL being used, not the one for the env I have created + selected.

    image (1)
    image (1)2162×798 82.7 KB

  2. If I go to view the defined variables it shows them empty

    image
    image720×352 26.8 KB

  3. Hitting the Check the auth status using current credentials seems to actually hit the correct env URL, but it's not passing the correct tokens so it fails on our end.

  4. We have some apps that let us use the TEMP env (eg it is not disabled). However when try to auth within a GQL query directly, this also uses the prod env even though I have another selected.

So to summarise, as far as I can see

  • Env disabled explanation isn't working
  • Testing custom auth flow isn't respecting the selected environment / correct environment variables

4) Additional info: (Cloud or Self-hosted, Screenshots)
Cloud hosted, screenshots above. Made a support request a week ago but no response.

3

Hi @horse,

Apologies for the issue. Can you show me a screenshot of the resource set up page and the full custom auth flow for the different environments?

Which env are you trying to use when the variables are showing the prod variables instead?

4

Also for the environment being disabled, the tool tip bug has been reported and I can add a +1 to that ticket for you.

In terms of what is likely causing that env to be disabled, if you have one single query that does set have setup added for that env, then it will prevent it from changing.

You can either remove a query that is not essential or you can make sure that all the resources being used in your app have all the environments added to their set up. This will likely get the new env to no longer be greyed out.

5

Hi @horse,

Just wanted to check if you had been able to find what resource or query was limiting the env switch.