Reserved parallel runs for manual testing

Problem
Teams with several parallel cloud runs often use all of them for automated suites (scheduled runs, CI/CD, API triggers). When someone needs to run a test manually, for example to verify a hotfix or debug a failure, they have to wait until an automated run finishes, because every slot is already taken.

What we’re planning
A concurrency limit for automated executions, set at the organization level. You will be able to decide how many of your parallel runs automated suites may use at the same time, and keep the rest free for tests started manually from the BugBug app.

Example: an organization with 10 parallel runs sets the automation limit to 9. Scheduled, CI/CD and API-triggered suites never use more than 9 runs at once, so 1 run is always free for manual testing.

How it will work

• A new setting in organization settings: “Max parallel runs for automated executions”

• Automated runs above the limit are queued, not rejected

• Manual runs can use any free slot, including the reserved ones

• Works within your current plan, with no change to your subscription or number of parallel runs