To clarify. The limitation has been applied only to running the entire collection via the âCollection Runnerâ within the app.
You can still run individual calls locally, and your entire collections via Newman, Postman Cli, or scheduling (monitors/webhooks) without being impacted by this imposed limit. (You are only limited when running the entire collection via âcollection runnerâ).
The Postman staff have (from what I have seen) been forthcoming on the community forum etc. by providing information about the new limits but also providing details on how else you can run your collections to workaround the limitations.
@woolsm if you are referring to âscratch-padâ then yes I believe this is also affected;
Your Postman plan gives you a limited number of collection runs you can use each month. This limit applies to collections that you run in a workspace or the Scratch Pad using the Run manually option. This limit doesnât apply to scheduled collection runs in the Postman cloud. A collection run with multiple iterations counts as a single run.
(Just my opinion) ⌠Itâs worth considering that the collection runner, while it appears to âonly run locallyâ actually syncs up behind the scenes so that the run results are accessible between client and browser but also cross team members etc. These underlying services and run histories etc. cost money to build and maintain and with Postmanâs ever-growing user base, it was inevitable that they would change their pricing at some point.
I know a lot of people probably wonât agree, but thatâs just my viewpoint.