Seems to me that there are some confusing communications out there…
Announce from Postman, email received the 1st May
• Collection Runner limit change: Moving forward, we are simplifying Collection Runner limits to 25 runs per user, per month for new plan purchases. However, for existing Professional teams, we are maintaining the previous limit of 250 runs per team, per month. If you would like to switch to the new user-based Collection Runner limit, submit a support request, and we’d be happy to transition your team. See our v11 FAQ for more information on Collection Runner changes.
Now, on the blog…
How many Collection Runs do users without the Collection Runner add-on have?
Beginning May 1, 2024, Postman users across all plan types will receive 25 collection runs per month with their base license. Previously, teams were limited to 250 collection runs per team/month.
Current customers on the Enterprise Essentials and Professional plans have the option to maintain the previous limit of 250 runs per team/month if they so choose. If you wish to switch to the old model with a team-based run limit, submit a support request. We are happy to honor this adjustment to your plan.
Should we ask the support to stay on a 250 runs/team/month ?
Or should we ask if we want to switch on a 25 runs/user/month ?
The email comms are correct, and the packaging blog has been updated accordingly.
We are maintaining the previous limit of 250 runs/team/month for existing Professional teams. Users can request to switch to new user-based Collection Runner limit of 25 runs/user/month.
Could we have a clear answer here ?
What will happend for a renewal ?
Will it fall automatically back to your new rule 25 runs/users/month ?
Keeping the 250runs/team/month will still be an option ?
I wanted to buy a licence but 25 runs per user seems to be extremely low for the price, especially when tools like JMeter are free (and more powerful IMO).
I’m just wondering if I missed something and don’t get what “run” means.
Is there clarity somewhere with definition of a run and what are the limitation (sic) for a paying licence?
Thanks
Using the collection runs to monetize the application by crippling an existing key feature instead of monetizing new features and development like the cloud CLI still seems like a crazy business approach to me. I do wonder if the reputational damage from this has started to kick in yet.
Yes 25 runs/person/month could be seen as extremelly limited (and it is, but it is not really a problem you can’t overcome, it depends on your workflow).
Regarding your team, maybe you could ask to migrate to the old 250 runs/team/month
=> I’ve never read that this was possible for a new licence.
Myself, I still don’t have any response regarding the renewal.
@danny-dainton : maybe you could answer to these two questions
From postman desktop :
A run is counted when :
you run a collection
you run a folder in a collection
Running a single request does not count for a run.
Advantage & limitations :
Runnnin a collection or folder :
you can use data file entry
you can loop a single request with specific data
you can branch to another request as long as it is is the same hierarchy
Running a single request : you can’t do anything of the above
Solution :
Use postman-cli
Use newman
I personnaly (and my team) use newman essentially for one reason : you can use custom reporter (postman-cli can’t)
I’ve never take time to test postman-cli essentially because of this.
There is no run limitation from the command line with newman (and surely/maybe postman-cli)
=> it count calls for postman api (for pro plan, this is 100.000/month)
When writing a new collection, I take care of not using to much collection/folder runs it the desktop app.
I tend to build a folder structure and run that folder with newman when I need to loop or branch to another request.
Limitation for newman : you can’t use the “package feature” of postman.
Ok thanks for this clarification. I’ll check newman.
It sounds strange they limit the amount of runs though. It is the limitation of a software running in the cloud. But it doesn’t make much sense here to me.
I realise that running a collection on desktop is using no resource on postman servers. I understand now it is better to run away from such a tool. License fee doesn’t make any sense. It’s a bit of a shame really.
Yes we currently use newman for our CI processes, but we are looking to move to postman cli to save the hassle of exporting collections and environments every time we make a change.
Its a real shame there is no support the html reports though I must admit. But being able to see the report inside the postman client is a new bonus, but not as pretty as the html reports
No, I didn’t to be honest, good point. I will look into that.
I take it with Newman I won’t be able to take advantage of the new features like the Package library though, which I’m keen to start using when it works in Postman CLI for us.
