I’m running the latest version of Postman, and I noticed that variables are no longer being interpolated when I hit Send.
When I hover over the variable, the tooltip shows the correct value.
However, both the Code Snippet panel and the actual Response clearly show that no preprocessing is being applied.
I’ve tried relaunching Postman several times and even switched between different environments and workspaces, but the problem persists.
Hey @mreis1 
Welcome to the Postman Community! 
I’m not currently seeing this in the latest version, the variables are resolved in the code snippet:
Do you have an Active Environment set when you were sending that request? It would show this if one is not set:
Do you have variables of the same name in any other variable scope?
If you could share a short video or a screenshot showing the fill app window, that would help up to see if anything else moight be happening here.
Hi Danny, I figured it out.
The bug occurs in a very specific scenario.
Setup:
Workspace A
Collection A
Env A
Env A1
Workspace B
Collection A
Env A
Env A1
(Note: I originally exported everything from Workspace A to JSON and imported it into Workspace B a long time ago. I repeated the export/import today just to confirm the behavior.)
What happens:
When I switch between workspaces, the environment variables are never preprocessed.
If I create fresh environment variables directly in each workspace, preprocessing works normally.
However, as soon as I switch back to any environment that was previously imported (via JSON), preprocessing stops working again.
I also noticed that opening the Environments panel from the sidebar, renaming one of these “imported” environments, and hitting Cmd + S temporarily triggers preprocessing—but after switching to another workspace and returning, the issue reappears.
So in terms of configuration everything is fine and nothing has changed in my environment from a long time.
Hey @mreis1 , could you help check one thing for debugging?
Do you happen to have any duplicate variables in this environment that are disabled? Specifically, does your active environment contain a disabled duplicate key for “url” or “token”? Something like this:
yes @aviation-saganist-61 . I can confirm that my environment matches yours. Some of the variables are listed more than once but disabled leaving only one active entry
Thank you @mreis1 for confirming! This really helps us narrow down the issue. We’ll provide an update here once the fix is released. In the meantime, as a workaround, you can try removing any disabled duplicates and restarting the app —this should resolve the issue until the fix is rolled out.
Hey @mreis1! We’ve fixed this in the latest Postman update (v11.73.4). Please update to the latest version and let us know if everything is working as expected.
