Limitations

This topic lists limitations for the current version of LoadRunner Cloud.

Load tests

The following table lists limitations for load tests.

Limitation Description Limitation
Number of concurrent tests

No limits apply to the number of concurrent test runs, with the following exceptions:

  • Trial tenants are limited to one concurrent test run.

  • Tenants created through an online purchase, are limited to five concurrent test runs.

Network emulation

Network emulation is only supported for the following protocols: No limits apply to the number of concurrent test runs, with the following exceptions:

  • Web HTTP/HTML
  • Mobile HTTP
  • Web Services
  • MQTT
  • TruClient Web
  • TruClient Mobile Web
  • SAP Web
  • Siebel Web
Enable multiple IP addresses Network emulation is not supported when this feature is enabled.
Wininet
  • Network emulation is not supported when this feature is enabled.
  • Scripts in which WinInet is enabled do not support multiple IP addresses.
Azure locations
  • You cannot use Azure locations for a test that enables multiple IP addresses from a load generator in the cloud.

  • Azure locations are not supported for tests that are configured for the WebPage Test report.

AWS locations
  • For the Beijing AWS region, script size is limited to a maximum of 80 MB.

Iterations run mode
  • The following features do not support the Iteration run mode:
    • Adding Vusers.

    • Manual and advanced scheduling for scripts.

    • Generating single user performance data.

    • The Timeline tab when scheduling a load test.

    • Changing the load in a running load test.

For details on configuring a load test's run mode, see Run mode.

Goal Oriented run mode

The following script types do not support the Goal Oriented run mode:

  • TruClient - Native Mobile scripts.

The following features do not support the Goal Oriented run mode:

  • Adding Vusers.

  • Generating single user performance data.

  • The Timeline tab when scheduling a load test.

  • Network emulations for cloud locations.

  • Changing the load in a running load test.

For details on configuring a load test's run mode, see Run mode.

Vuser log collection Collecting Vuser logs may cause the load test to take longer to stop after it has run.
Pause scheduling

The following limitations apply to the pause scheduling option:

  • This feature does not support the Goal Oriented run mode.

  • When pausing is enabled, the following features are not supported:

    • Adding Vusers
    • Single user performance
    • Changing the load when running a test

For details on pausing a schedule during a run, see Pause scheduling.

Back to top

Agents

The following table lists limitations for agents.

Limitation Description Limitation
Federated users LoadRunner Cloud on-premises agents (such as load generators, Git agents, streaming agents, and monitors) do not support federated users.

Back to top

Monitors

The following table lists limitations for monitors.

Limitation Description Limitation
Monitor types You can only add one monitor type to a test definition.
SiteScope on- premises
  • If you select or clear the Disable integration check box in the SiteScope configuration, but the agent continues to behave as it did before you made the change, restart the SiteScope service.
  • If a monitor that you did not select appears in the monitor gallery, stop the load test, and reset the SiteScope agent and the SiteScope service.
SiteScope on-premises Docker integration Standard application monitors deployed during runtime are not supported.
Dynatrace
  • Dynatrace dashboards designed with rich clients are supported, however, dashboards designed with Web clients are not supported.

  • For Dynatrace SaaS monitors, metrics are shown with a delay of approximately two minutes. This means that a load test that runs for less than three minutes may not display any metrics.

AppDynamics

Metrics are shown with a delay of approximately two minutes. This means that a load test that runs for less than three minutes may not display any metrics.

Application Insights

Metrics are shown with a delay of approximately two minutes. This means that a load test that runs for less than three minutes may not display any metrics.

Back to top

Scripts

The following table lists limitations for scripts.

Limitation Description Limitation
LoadRunner scripts Scripts created with versions prior to LoadRunner 12.0 are not supported.
LoadRunner cross Vuser transactions Not supported.
LoadRunner rendezvous points

You cannot dynamically change the load of scripts that contain rendezvous points.

For details on working with rendezvous points, see the LoadRunner Professional Help Center (select the relevant version).

LoadRunner mobile protocols Support for Mobile Application-HTTP/HTML, TruClient Native Mobile, TruClient Mobile Web.
Web HTTP/HTML Snapshots Not supported.
Wininet Network emulation is not supported when this feature is enabled.
Maximum values
  • The script size cannot exceed 200 MB.
  • The maximum number of scripts that can be added to a load test is 100 for trial versions and 500 for non-trial versions.
  • The maximum number of scripts that can be uploaded to a tenant is 500 for the trial versions and 30,000 for non-trial versions.
TruClient scripts
  • Script is stopped if it hangs for more than 10 minutes.
  • TruClient scripts can run with emulation on Firefox or Internet Explorer only.
TruClient Script Converter Supported for Windows only.
TruClient script created with Firefox .xpi Not supported.
Localized support LoadRunner Cloud supports scripts written in non-Latin alphabets. However, you still must use Latin characters for file and folder names.
Additional Vusers Adding additional Vusers is not supported if the test uses network emulation.
64-bit Replay 64-bit Replay of LoadRunner scripts is not supported.
Script and transaction names Script and transaction names cannot contain a comma.

Back to top

Runtime settings (RTS)

The following table lists limitations for runtime settings.

Limitation Description Limitation
Proxy settings

If your script is configured to run with proxy settings that are inaccessible from outside your local network, LoadRunner Cloud may ignore RTS settings. Disable the proxy settings and run the test again.

If the issue persists, open a support case.

Run Vusers as a process This option in a script's runtime settings is ignored and Vusers always run as threads. To request enabling Vusers to run as a process, open a support ticket.

Back to top

Single user performance data

The following table lists limitations for single user performance data.

Limitation Description Limitation

Number of scripts

  • NV Insights report. You can specify one script per test.
  • TRT breakdown. You can specify up to five scripts per test.

Script type

Only Web HTTP/HTML, TruClient Mobile Web, TruClient IE, TruClient Chrome, and TruClient Firefox scripts are supported.

Your script is configured to run with proxy settings that are inaccessible from outside your local network

TRT breakdown widgets and the NV Insights report will not generate.

Disable the proxy and run the test again.

If the issue persists, open a support ticket.
NV Insights report limitations
  • The network scenario is displayed as default scenario.
  • Total throughput per transaction is not supported.
  • The NV Insights report does not support scripts in which WinInet is enabled.
WebPage Test report
  • Generating a WebPage Test report will add additional time (10 to 20 minutes after the last running Vuser is stopped) to your test run.

Back to top

Reports

The following table lists the limitations for (new) reports.

Limitation Description Limitation
Add Notes Text formatted in italics displays as regular font in the PDF.
Number of transactions

If you have more than 5,000 unique transactions, export to Word/PDF will be disabled.

Custom report

You can include a maximum of 10 snapshots per report.

Raw transaction data

When you export raw transaction data to a .csv file, the following limitations apply:

  • This option is supported for on-premises load generators version 3.6 and later.
  • Only transactions that passed are included.
  • Transaction groups are not included.
  • A maximum of 100 million entries can be stored.
  • The data is retained for one week, after which it is automatically purged.
Raw script error data

When you export raw script error data to a .csv file, the following limitations apply:

  • This option is supported for on-premises load generators version 3.5 and later.
  • The report includes a column for transaction ID. This column is populated only for MDRV script protocols.
  • A maximum of 500 thousand entries can be stored.
Load generator log files
  • The maximum log file size is 512 MB for on-premises load generators and 1 GB for cloud-based load generators. Log files that exceed the maximum size are not included in the exported logs for a test run.
  • The total size of all the log files included in a download cannot exceed 15 GB.

Back to top

Dashboard

The following table lists limitations for the (new) dashboard.

Limitation Description Limitation
Widgets
  • For best performance, do not display more than 8-10 widgets on the dashboard at one time.
  • If the number of metrics in a widget exceeds 1000, only 1000 results are displayed per tab. The comparison view shows 1000 per result set for a total of 2000.
  • The maximum number of tabs that you can open is 20.
Snapshot on error
  • The number of snapshots generated per test is limited to 20.
  • For each unique error id, only one snapshot is generated.
Data latency In rare instances, results returned after several minutes were updated to a previous data point within the test run.

Back to top