If your organization has multiple teams sharing a Sauce Labs account, it's important to monitor your concurrency limits, the number of virtual machines that you can run tests on simultaneously. You'll need to ensure that your organization's concurrency is distributed among your accounts and sub-accounts, rather than allocating all of it to a single sub-account.
How Concurrency Limits Work
Only Organization Admins have the privileges to set the total concurrency of their organization's Sauce Labs account. When setting the concurrency limit for a team/sub-account, be mindful that by default, each team member will inherit the concurrency limits of that entire sub-account. If there are enough members on that team, their combined concurrency allocation could easily consume the concurrency allocation for the entire organization.
In the diagram below, "OrgX" has a total concurrency of 100 VMs, and the Org Admin allocates 20 VMs to their Apps Team, which has five members. This means that each member can run 20 VMs at the same time and max out the organization's 100 VMs limit. To avoid this scenario:
- Set the concurrency limit for each Apps Team member to 4, so that if all members run tests at the same time, they'd be consuming 20 VMs. The topic Adding Users to Your Account > Step 7 describes how to do this.
- Instead of setting up each team member up as a member of the sub-account, have them share the the overall Apps Team account without creating individual accounts for each of them
Once you've used all of your concurrency slots, additional tests will not start until an existing test finishes. As tests complete, queued tests are allocated to concurrency slots in the order they were queued, however, we do not recommend queuing tests intentionally. Tests will time out with an error if they are queued for too long and/or if too many tests are already queued.