Is Postman 10.20 still stable for automation

Help Hub
,
1

Hi Team,

We recently downgraded from Postman 11.x to 10.20 due to issues with the Save button, autosave instability, and syncing failures.

Before we standardise across the team:

  • Is 10.20 still considered a stable version for API Test Automation and Collection Runner usage?

  • I have observed that my curretn varibales are not exporting to others to utilise

  • If we should switch to an 11.x release instead, which exact 11.x version is currently the most stable for automation work?

  • Does Postman recommend a particular long‑term stable (LTS‑like) version?

Thanks in advance.

1 Like
2

Hey @kirankumar-elchuri :waving_hand:

Welcome to the Postman Community! :postman:

Can you provide some additional context for the selected version?

We have just released v12 so that would be 2 major versions behind. I would recommend being on the latest version of the platform to ensure that any issue that you face, will be investigated and fixed.

For versions like v10 this is not going to be the case and this will continue to be lacking both features and vital updates. The variable experience has been significantly changed since v10.

1 Like
3

Hi Danny,

Thanks for your quick answer!

We are happy to upgrade — we just need assurance that the Save/Autosave issues are resolved

Our intent is not to stay permanently on 10.20.
We only want to avoid introducing instability into our Test automation framework.

If Postman leadership can confirm a recommended stable version, we can align our entire team to it.

4

Without knowing the full details of the save or autosave issues that you were encountering and against which version, it’s difficult to share anything related to that.

Is this part of it?

  • I have observed that my current variables are not exporting to others to utilise

The current variables (This experience has changed now) would not be part of any exported file or seen by teammates as those are session based and local to you. Initial Variables would have been Synced/Shared and be the value within an exported file.

1 Like
5

**Hi Danny,

Regarding the Save/Autosave concerns: yes**, the issues we encountered are consistent with several publicly reported defects in later Postman releases (11.74). To provide more context, here are the specific stability problems that influenced our temporary downgrade:

1. Save Button Failures in Newer Versions

There are multiple GitHub issues where users on Postman 11.70 reported that the Save button becomes unresponsive or disabled, preventing changes from being committed to collections or environments.
This aligns exactly with what we observed internally — newer versions sometimes do not provide stable or reliable save behavior.

2. Autosave and Sync Instability

Community discussions indicate that Autosave is:

  • inconsistent across releases,

  • missing entirely for some users, and

  • unreliable when syncing changes across workspaces.
    This undermines confidence in the auto‑locking and autosave mechanisms that later versions depend on.

    3. Documented Loss of Work and Corrupted Updates

Several users report scenarios where edits appear timestamped as “saved” but do not persist, and in some cases they need to switch to the web client to recover work.
This has been a recurring theme in the community and presents a real operational risk when teams manage large, complex API collections.

4. Productivity & Stability Impacts

Because of these regressions, several users and teams intentionally remain on older versions for stability.
This mirrors our situation and supports to continue using Postman 10.20.x temporarily, as newer versions introduce risks that could disrupt test automation workflows.

6

Hi @danny-dainton,

Can you please advise us on the above issues please.

7

Your response was an AI generated summary of some specific issues that other user we’re potentially having.

I can’t comment on other people’s reported issues as that happened to them, in their context, on a particular version.

You haven’t provided any links to those reported issues for me to begin to establish the context of those issues.

You haven’t actually demonstrated any of the problems you have faced, with visual examples and steps to reproduce. Without that, I’m not going to know exactly what happened for you.

My only recommendation would be to use the latest version, as that’s fully supported and any issues that do happen, will be fixed and deployed.