UiPath Documentation
test-manager
latest
false
Test Manager user guide

Known limitations for performance testing

Known constraints for performance testing in Test Manager, including robot runtime limits and maximum concurrent jobs.

Execution duration limits​

Cloud, serverless robots can run for a maximum of 60 minutes per test. On-premises robots can exceed this limit.

Concurrency limits​

  • Maximum concurrent jobs: Up to 500 jobs can run concurrently using serverless robots.

  • Impact on virtual users (VUs) — serverless: The number of achievable virtual users depends on multiplexing (multiple VUs per job). For example, with a multiplexing factor of 4, a scenario can scale up to 2,000 concurrent virtual users.

    • This factor is automatically detected during the dry run and reported in the application logs. It cannot be manually overridden for serverless robots.
  • Impact on virtual users (VUs) — on-premises: On-premises robots are not capped at 2,000 VUs. With sufficient licensing, the dry run can compute a higher achievable virtual-user count, up to a hard maximum of 10,000 concurrent virtual users. Unlike serverless robots, the multiplexing factor here can be manually overridden.

  • VPN constraints: When using a VPN, the effective concurrency depends on the VPN or gateway capacity.

    • Default limit: ~250 concurrent jobs
    • The actual limit may vary based on the gateway SKU and infrastructure capacity.
    • If higher concurrency is required, customers should contact UiPath support or their account team to discuss VPN scaling options.
  • Execution duration: Serverless robots are limited to 60 minutes per execution

Application type override​

You can change the application type of a load group only from Desktop to Browser. The override applies to a single load group.

Supported automation types​

Performance testing is currently limited to Browser, API (HTTP WebRequest), and Desktop automations. For example, Integration Service or coded automations are not yet supported.

Within these supported automation types, Workflow Analyzer now flags specific unsupported activities automatically during dry run — see Creating automated tests for the current list.

Additional limitations​

Performance Testing measures only the following:

  • Load
  • Response time
  • Error rate
  • Throughput

It does not collect application- or system-level monitoring metrics (CPU, memory, database, infrastructure). Existing APM/observability tooling covers that data instead.

Programmatic access to performance test data is available at the scenario level: the API can return execution metrics for a specific scenario ID, which you can use to build your own historical tracking (for example, exporting results after each run for later comparison).

No API exists for comparing execution metrics across two or more scenario runs, or for retrieving an aggregated historical summary across runs. Within the product itself, the Comparing performance results view supports this.

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated