Portal Login
A portal login will time out after 4 hours of inactivity.
Node-based Tests
Download Limit
There is a limit of 15MB per Page and per File. If you would like to increase the download limit for a particular test, learn more here.
Thresholds for Common Metrics
| Metric | Threshold |
|---|---|
| File Size | 15 MB |
| # of Requests | 2000 |
| # of Hosts | 255 |
| # of Requests per Domain | 500 |
| Page Size | 15 MB |
When the above-mentioned thresholds are exceeded, the Catchpoint tests return the following errors:
| Error Code | Name | Description |
|---|---|---|
| 50012 | OtherTooManyBytesUrl | The URL reached the maximum size limit |
| 50004 | OtherTooManyUrls | The test reached the limit of 1,200 Request URLs per test |
| 50007 | OtherTooManyDomains | The test page reached the limit of 255 unique domains per test |
| 50008 | OtherTooManyUrlsPerDomain | The test page reached the limit of 1200 request URLs per domain. Other URLs were not logged or reported |
| 50013 | OtherTooManyBytesTest | The test page reached the maximum file size limit |
| 50107 | Too much time elapsed to run the test | The test page has reached the maximum time the test can be run |
| 50020 | OtherTooManyBytesTestFromObjectUrl | The test was stopped because a request URL exceeded the allowed size. |
Total Time to Run a Test
Web Tests: Up to 30 seconds for the entire test is the default. However, this can be changed in the Advanced settings on a per-test basis. You can choose 5, 10, 20, 30, 60, 90 or 120 seconds. Note that any time above the default may impact point usage.
Transaction Tests: The threshold is 60 seconds per step. So, for a two-step Transaction test, the limit is 120 seconds. However, this can be changed in the Advanced settings on a per test basis. You can choose 5, 10, 20, 30, 60, 90 or 120 seconds per step. Note that any time above the default may impact point usage.
Also note that time from pause() or waitForNoRequest() commands, if used in your test, will not be added to the Webpage Response metric, but will count against the overall test timeout threshold.
The following are some examples of the total time limit for transaction tests using the default time.
A three-step Transacation test has a total time threshold of 60 seconds x 3 = 180 seconds. The below test will timeout:
Step 1 - 20 seconds
Step 2 - 120 seconds
Step 3 - 100 seconds
Total - 240 seconds > 180 seconds
For a five-steps test, the total time for the threshold is 5 x 60 seconds = 300 seconds. Below you can see how the agent can wait up to 60 seconds per step.
Step 1 - 40 seconds
Step 2 - 120 seconds
Step 3 - 110 seconds
Step 4 - 20 seconds
Step 5 - 10 seconds
Total - 300 seconds
However, When we apply a per-step override on a Transaction test, the timeout is enforced per step. For example, If we have a two-step transaction test and set the enforce test failure to 5 seconds per step, 6 seconds on Step 1 will lead to step failure and the test will not continue to Step 2.
Maximum Number of Characters
- Test Name: 128 characters
- Test Description: 255 characters
- Label Name: 128 characters
- Label Value: 128 characters
- Transaction script: 40,000 characters
Randommacro List: 4,000 characters- Web/Transaction Instant Tests: 256 chars for Request Settings in the value
- Global Variable Name: 32 characters
- Global Variable values: 1,024 characters
Maximum Number of Tests in a Product/Folder
The maximum number of tests that can be added to a product/folder is 1000.
Maximum Number of Global Variables
Per division there is a limit of 500 on the back-end.
Per test there is a limit of 32 global variables that can be set.
Maximum Number of Labels in a Test
The maximum number of labels that can be assigned to a test is 100.
Maximum Number of Steps in a Transaction Test
Transaction tests can be up to 25 steps long. If there are more than 25 steps in a Transaction Test script you will receive the error message: "Invalid Script: Too many transaction steps.".
Maximum Number of Steps in an API Test
An API test can be up to 25 steps long just like a transaction test.
- If there are more than 25 steps in an API Selenium Test script you will receive the error message: "Invalid Script: Too many transaction steps.".
- If there are more than 25 steps in an API JS Test script the test will fail after 25 steps with the error message: "[50105] - The transaction contains too many steps.".
Hops in a Trace Route Test
A Trace Route can take up to 30 hops and can have up to 6 consecutive hop failures.
Maximum Request Size for Response Capture
This limit does NOT impact a test's success or failure rate since it only determines how much of the downloaded data is stored. For Web/Transaction tests, the first 200KB is captured for the base URL, and for child requests, the first 20KB is captured. Also, For captured data, request & response headers are configured to a 8192 character limit, while the response content limit is 20,000 for child requests, and 200,000 for root requests.
Maximum URL and POST data limit for JS API
There is a char limit of 2048 characters for the url and 20,000 characters on POST data for JS API monitor.
Real User Measurement
Page/View URLs have a maximum of 10,000 in system data views. Custom data views have up to 500 or 2000 (if non-distributed) different breakdown value per hour. There is no limit for # of URLs in Explorer.
There is no limit to the number of values for tracepoints in Explorer. In dataviews, we allow up to 1000 values per tracepoint per hour.
Most other dataviews (for other dimensions) allow up to 100k values per hour.