Request Chaining And Swapping Environments

Just first up, thank you for this app. I’ve been looking for a way to leave Postman and you are delivering them in spades. Its refreshing to have a performant and enjoyable to use application for this kind of work.

—

I’m not sure if this is intended behaviour or not but when switching environments, the value in an ‘When Expired’ response.body.path value is maintained. I’m using it to authenticate my calls and when switching environments that token (which is still valid in another environment) is being used in this other environment’s calls.

The steps to reproduce are…

1. My workspace inherits the Bearer token authentication method

2. The token value comes from a Get Token call request chain with an expiry

3. Making a call in one environment gives me a successful authenticated request chain

4. Swapping to another environment I get 401s as the second environment is trying to use the first environment’s token

5. Manually calling the Get Token request seems to update the value and requests now work in this environment

6. Swapping back has the same issue where the first environment’s requests are no longer working because it’s trying to use the second environment’s token

I tried using folder level settings for this but that didn’t seem to change it. If this is intended behaviour, would there be a way to include a toggle to share across environments or not? Even just a ‘drop value when switching environments’ would be amazing.

It’s kind of low priority for me since my workaround is to switch it from When Expired to Always which ensures that each request is using it’s environment’s token but does add some noticeable latency to calls.

Thanks so much