Are you aware of an issue where editing variables gets delayed, and the request is made with the previous value?
Doesn’t matter the way you change them, which could be via the hover menu for variables or the “variables in the request” sidebar.
You can see the old value by looking at the console or using https://postman-echo.com/get?v={{test}} to see its response. Or even by doing invalid operations on the endpoint you are using.
I never took the time to request support about it, but it’s driving me nuts more and more.
It started months ago, maybe when the new UI for variables was deployed. It’s really curious that I can’t find anyone complaining about it here in the community. It affects multiple people in my team.
I recorded a short video to show the issue. It’s easier to see the problem by quickly changing the value and sending the request, but sometimes it happens even after waiting more than a second.
It’s pretty easy to fall into this problem if you are pasting a value in the variable field before sending the request.
If you just repeat the request, it may send the new value.
That does look like an issue, the recording was very appreciated to show the problem.
I’ve flagged this internally with the team to take a look at and investigate.
It looks to been an issue with the speed of the operation, do you see the same issue if you slightly slow down the process of changing the value and sending the request?
I’ll come back and share any updates that I have from the team once they have had a deep look into the issue and found the root cause.
The easiest way to reproduce is being fast, but I really try to go easy before submitting the requests, and it’s frequently insufficient.
Consider that there’s not much more to wait while pressing Cmd+V, Enter, Cmd+Enter to paste, set the value, and submit the request.
But it seems that the delay may vary with the app’s performance, where Postman can be really slower due to multiple/heavy tabs. The video was recorded with a single tab for privacy purposes.
Hey @garrucho! Thanks for sharing the details, we’ve fixed this in the latest Postman update (v11.62.5). Please update to the latest version and let us know if everything is working as expected.
Now, it’s waaaaaaay less sensitive. If I really force myself to go fast, I can still get outdated values (something that doesn’t happen by directly updating a field, without a variable), but I agree this is exaggerated and not a human behavior anymore. So, commenting just for the sake of QA.
This will make a difference in a routine of constantly pasting and submitting values. Kudos to everyone involved.
So, commenting just for the sake of QA.