In Functionize, a test execution may be placed on hold or fail to start if your account has reached its concurrent execution limit. This happens when the maximum number of test runs allowed to execute simultaneously for your account are already in progress.
How Concurrent Execution Works
Concurrent execution refers to the number of test runs that can execute at the same time under your Functionize account.
When a new test run is triggered:
Functionize checks whether an execution slot is available.
If a slot is available, the test begins execution immediately.
If all available slots are already in use by other running tests, the new test is placed in a queued or on hold state.
The test will remain on hold until an execution slot becomes available.
Execution Limitations
When your concurrent execution limit is fully utilized:
No additional tests can start execution.
New test runs remain in a queued/on hold status.
A queued test will only begin execution when:
A currently running test completes, or
A running test is manually stopped by a user.
How to Resolve Queued Tests
To allow queued tests to start:
Wait for existing test runs to complete, or
Manually stop one or more running tests to free up execution slots.
If you frequently encounter this limitation, consider reviewing your execution usage.
Understanding Disabled Tests in Orchestration Runs
The system may log DISABLED_TESTS when test cases remain in the agent queue for an extended period. This is an expected system behavior designed to prevent indefinite waiting when execution resources, such as agents or browser VMs, are heavily utilized and unavailable.
How It Works
Even if the overall concurrency limit has not been reached, jobs can be delayed if agents or browser VMs are temporarily unavailable. This results in a high Agent Queue Time, which is the period when the queue is blocked because no agents are available to pick up new test cases. If jobs remain in this queue for an extended duration, the scheduler automatically disables the remaining test cases to avoid an indefinite wait.
Limitations
This behavior is directly related to the availability of execution resources, not to any issues with the test scripts or their configuration. The key factor is the temporary unavailability of agents and browser VMs, which causes high queue times and scheduling delays, even if the concurrency quota has not been met.
Related Info
To resolve this issue, re-run the orchestration once sufficient execution resources (agents and VMs) are available.
