Hello Postman team,
We’re experiencing an issue where the Collection Runner is consistently delayed by 30 seconds before each run. The message says we’ve hit the collection runs limit on our plan, even though we’re just trying to run basic test collections locally.
This delay happens every time and severely slows down our testing workflow. Is there a way to disable or bypass this timer, especially when running collections locally and not via the Postman cloud infrastructure?
Any clarification or help would be appreciated.
Thanks in advance!
Hey @spacecraft-enginee13 
Welcome to the Postman Community! 
Each plan has usage limits which determines how many times something can be done in the UI, these are reset each month.
The Collection can be run is different ways like using a Monitor or using the Postman CLI in a terminal, each of these has a different set of limits but will allow you to run Collections and see the results of these.
The Postman CLI also have the added benefits of creating external reports based on your runs that could be shared in HTML, JSON and XML formats. The runs made via the Postman CLI are also shown in the Runs section of the Collection.