Bug in environment variable substitution in flow HTTP request

Hey Flows team (and likely @flows-daniel :slight_smile: ),
I believe I’ve found a minor bug in environment variable handling within the HTTP request block. The following request works fine in the Collections view and all env vars are substituted properly there. The var in question is bitbucketWorkspace - note that it’s blue - and if I hover over it, it does see the value stored in the Environment.

However, when this block is run, this is the resulting request:
image

So I thought I’d replace it with a different var, in the same Environment, that had the same value, but had the same result:
image

Finally, though, I replaced it with the same var name, but stored in Globals, and it worked!
image

It is worth noting that the protocol, host, and basePath vars are all in the Environment store and they resolve perfectly fine!

I’ll leave it in your capable hands, since I clearly have a workaround. Thanks!

Hi @distorto666

You have to add the environment to the request where it says add environment :slight_smile:

The top right environment selector doesn’t work with flows.