One genuine mistake: “Why Isn’t This Updating?”
While working in a shared Collection in Postman, I updated a request test to fix a failing assertion. I ran it again. It still failed. I tweaked it. Ran it again. Still failed.
When i was using postman for first time after 10 minutes of debugging, I realised something embarrassing: “I never clicked Save”.
The Collection Runner was executing the previously saved version of the request not the changes sitting in my tab. Even tho i know now it still happens lol.
What I was trying to achieve: Fix a failing test before pushing to the team workspace.
What went wrong: I assumed Postman auto-saved.
How I realised: I opened the request in a new tab and saw my “fix” wasn’t there.
What I changed: Now I hit Ctrl+S before every run.
And I double-check the “unsaved changes” dot before running collections.
Lesson: Sometimes the bug isn’t logic.
It’s muscle memory created using code editors or other tools.
If u ever see dots likes these on top of your requests please save before u proceed.
