I’m encountering an issue in Postman for Windows where updated input values and environment variables aren’t saved properly, even after explicitly saving them.
Steps to Reproduce the Issue:
- Open Postman for GraphQL and edit input values or environment variables.
- Save the changes.
- The updated values are displayed as expected.
- Run a GraphQL mutation or request that uses the updated input/environment variables.
- The mutation still uses the old values, despite the UI showing the updated ones.
- Close and reopen Postman.
- The old values are restored, and the updated ones are gone.
- Re-edit and save the variables. After doing this, the updated values persist.
It seems that in the current version of Postman, changes to variables or input values are only saved successfully on the first attempt.
Platform Details:
- Postman for Windows
Version: 11.21.0
UI Version: 11.21.0-ui-241119-0633
- Desktop Platform Version: 11.21.0
- Architecture: x64
- OS Platform: Windows 10.0.22631
Expected Behavior:
Changes to variables and inputs should persist after saving them and should be used during mutations or requests.
Observed Behavior:
- The UI reflects the new values immediately after saving, but the old ones are used in requests.
- Closing and reopening Postman reverts the variables/inputs to their old values unless re-saved.
Has anyone else experienced this issue? Any workarounds or fixes would be appreciated!
Hey @maximilianfixl 
Welcome to the Postman Community! 
Could you provide a short recording or screenshots of the behaviour you’re seeing, please?
If make it easier to visualise the problem and potentially see some information that you may not have shared in the description.
Hi @danny-dainton!
Thank you for your message.
At the moment I have tried it on another place and here the input variables are sent without problems (even without saving).
I will have a look at the other PC this evening to see if the problem persists.
Is it possible to delete a cache in PM or otherwise try to solve temporary problems without having to wait for an update?
Does it perhaps help to empty /temp or other Windows directories locally, which might cause PM not to update the varbiables immediately?
Here’s another screenshot (even if it’s of the current instance working as expected).
I will keep you up to date.
Best,
Max
Thanks for providing the update here - With that new information, I can see that you’re using a GraphQL request and GraphQL variables, which wasn’t clear from your original post.
Those are statically entered variables, I can’t see anything in that screenshot that would suggest that those would change but you did mention that you’re doing that manually right?
You could try enabling the Autosave option to avoid/reduce the risk of having unsaved requests:
There is a Clear Cache and Reload option in the menu bar of the Desktop App
1 Like
Hi @danny-dainton!
I apologize for not mentioning usage correctly in the original post. I probably thought the mention of mutations in my bubble was sufficient. 
Thanks for pointing out how to clean the cache. Yes, I manually adjusted the input variables in this example. In my instance, where there was no problem today, the beta function “Auto Save” is deactivated.
I’ll definitely have another look at this on my other PC and give you some feedback.
Best,
Max
1 Like
Hi @danny-dainton,
Now some time has passed and I still have (am I really the only one?) the problem that the input variables do not update. Meanwhile, I am on version 11.22 and can confirm independently of the machine that the variables are not being saved.
Current observation:
Start Postman → open mutation → change input variables → the orange dot appears signaling me that there is something to save. 
Execute mutation → expected data was sent (updated input).
Change input variable again (whether in this or another tab does not matter) → no orange dot appears and I cannot save. However, my updated input is displayed as last changed by me. 
Exit Postman → start Postman → old input variables are displayed again → change input variables again → orange dot appears again and you can save.
This process is repeated each time the input variables are changed. It seems that you can currently only save the changed request once. Unfortunately, this is very tedious for API development.
Can you have another look here with the team to see if you can reproduce it? Making a video would be relatively time-consuming. Alternatively, I can present it via other channels if you can’t reproduce it.
Regarding your previous tip to deactivate auto save first: It is deactivated for me. However, it makes no difference.
I look forward to receiving your feedback.
Best,
Max
