When using postman flows to run an api, the path is:
{{base_url}}/site/:siteId/
base_url resoves to: Global - https://{{name}}.{{url_suffix}}
name resoves to: Collection - service_name
url_suffix resoves to: Global - {{env}}.net/api/v{{ver}}
env resoves to: Environment - env_name
ver resoves to: Global - ver_int
I get the error:
getaddrinfo ENOTFOUND service_name.{{env}}.net
It looks like base_url is resolved and nested references name and url_suffix are also resolved, but not env (within url_suffix)
Why does {{env}} not resolve?
As a side note, when running the API directly in the collections, all the variables resolve with no issue
@danny-dainton
Hey @satellite-cosmonau10 
Welcome to the Postman Community! 
It might be also useful to show a screenshot of the Flow to show this setup - It might be something simple like a certain environment not set?
Are you using any type of script in the requests, that help to resolve those variables variables?
I’m not an expert in all things Postman Flows so I’ll need to call in backup here. cc @flows-daniel @Rodric-Rabbah 
Hey,
Thanks for the reply
In Flows:
In Collections:
In this example the env resolsed as expected to “qa”
Does selecting the “Add Environment” button on the that request block and using the same Active environment you have for the main request work?
1 Like
Thanks!
I never noticed that option.
This does make Flow building with environment quite cumbersome…
Needing to add the environment per block.
In addition, changing environment for using the same APIs would be really cumbersome with Flows
Is there no way to globally use the selected environment (in the top right corner)
1 Like
Not today. We recognize this is not ideal, and we’re working on a solution (few weeks away).
2 Likes
