Rest query headers not updating per environment

Queries and Resources
1

  • Goal:
    Trying to set up different header values on my Rest query resource based on the prod vs staging environment.

  • Steps:

  1. Go top prod env set a new custom header "api-key=xxxxxx"
  2. Click save
  3. Switch to staging env edit the header value to "api-key=yyyy"
  4. Click save
  5. Hard refresh the page, both prod and staging still have the original value from PROD.
2

Hey @amith!

This is definetly odd behavior and something for the Retool team to look into, but I figured I may chime in here.

How are you updating the resource? Using the edit button within an app, or using the resources section? I have experienced issues before editing in the app, so its worth trying the resources tab.

When you make a change / hit save, do you see any errors in the browser dev tools console (Shift + CTRL + J). This may be useful to narrow down the issue.

Hopefully this can help work towards a solution quicker!

3

Thanks @jamesg31
I was doing it from resources tab.
And I dont see any error in the dev console.

Surprised no one is seeing this problem ?

4

Hi @amith we have a bug in our queue to be fixed where the value shows incorrectly on the resources page. According to our testing, it works as expected in the app. Is that what you're seeing?

5

Hi @Tess I am not seeing it work correctly in the app as well.
Its only taking one value, either prod or staging irrespective of which env the app is running into.
This breaks our prod app in favor of staging app or vice versa.

6

Would you be able to share a screen recording that I can pass along internally? I am having trouble reproducing this for them

7

Thanks @Tess
Actually you right, the values are just reflected on actual app, but resources tab shows them incorrectly.
I have switching back and forth, and just lost track what was working vs what was not.

Good to know as a workaround for now...

8

Ok I'm glad it works in the app. It is still a terribly confusing bug :disappointed: I will let you know once our team has shipped a fix

9

@Tess Hello! Our team has been dealing with this issue as well, it's quite misleading to say the least. Any ETA on a fix?

10

We have someone working on fix, but I don't have an eta yet :disappointed: It's still dependent on how long it'll take to test/review the fix

1 Like
11

Hi everyone, our team shipped a fix for this issue. When you have a moment, I'd love to hear if you're seeing an improvement on your side