By default, LoadView allows up to 15 minutes for script execution during a load test. If the script does not complete within this time frame, the system marks the test session as failed, generates an error and aborts the script execution.
If you need to simulate a complex user journey or workflow that requires extended interaction time on the target application, you can extend the script execution timeout to a maximum of 50 minutes by adding a time threshold directly to your script.
Before extending the script execution timeout, learn how a script duration longer than 15 minutes can affect test validation and test scenario configuration, and how to handle these differences. See Considerations for Session Durations Longer Than 15 Minutes.
How to Set a Custom Script Timeout
To increase the script execution time limit, insert the following command into your script:
SendEndScriptTimer(TimeSpan.FromMinutes(25));
This example sets the script execution timeout to 25 minutes. If the script runs longer than the specified duration, it will be automatically aborted.
If multiple SendEndScriptTimer commands are included in a script, only the last one will be applied during execution.
The SendEndScriptTimer setting is not applied during test validation. Validation runs with the default 15-minute timeout. If your script exceeds this limit during validation, you may see a timeout error. This error can be safely ignored—your script will run with the configured timeout during the actual load test.
Considerations for Session Durations Longer Than 15 Minutes
If the configured session duration is longer than 15 minutes, the validation limit affects:
- The Estimated Sessions value on the Test Scenario page.
- The number of CSV value rows required for Unique per Session mode.
- Validation timeout messages.
These values can differ from what you expect because validation uses a 15-minute session window, while the actual test uses the configured session duration.
| What you see | Why it happens | What to do |
|---|---|---|
| Estimated Sessions is higher than expected | The estimate uses a 15-minute validation duration instead of the configured session duration.
For details, see Estimated Sesions |
Calculate your own estimate: virtual users × sessions per user, based on your configured session duration. |
| Unique per Session requires more CSV rows than expected | The row requirement is based on Estimated Sessions.
For details, see Unique per Session Mode |
Upload enough rows to meet the displayed requirement. |
| A validation timeout occurs | Validation stops after 15 minutes, regardless of the configured session duration.
For details, see Validation Timeout Errors |
Safe to ignore – if the timeout occurs only during validation, it does not limit the session duration of the actual test. |
During test scenario validation, LoadView runs the script to measure Session Duration: the time required for one virtual user to complete a session.
LoadView uses the measured session duration, the number of virtual users, and the total test duration to calculate Estimated Sessions.
If the configured session duration is longer than 15 minutes, validation stops at 15 minutes. LoadView can use 15 minutes as the measured session duration when calculating Estimated Sessions, even if the actual test uses a longer session duration.
As a result, Estimated Sessions can be higher than the number of sessions the test is expected to generate.
Example
Consider a test with:
- 10 virtual users
- 60-minute test duration
- 30-minute session duration
During the actual test, each virtual user can complete approximately two sessions. The test can therefore generate approximately 20 sessions.
If validation measures only 15 minutes, LoadView can calculate the estimate using a 15-minute session duration and display approximately 40 Estimated Sessions.
This difference does not indicate a problem with the script or test configuration.
Unique per Session Mode
If your test uses a dynamic variable with the Unique per Session row use mode, the CSV file must contain at least as many value rows as the Estimated Sessions value.
If the 15-minute validation limit increases the estimated session count, LoadView can promt you to upload a CSV file with more rows than the test is expected to use. To handle the row requirement, upload enough rows to meet the displayed Estimated Sessions requirement.
Validation Timeout Errors
A script with a session duration longer than 15 minutes can reach the validation timeout before the session completes. This can occur even if you use SendEndScriptTimer to increase the script execution time for the actual test.
If the timeout occurs only during validation, it does not limit the session duration configured for the actual test. The test can run for the configured session duration.