The error message Global Script Execution Timeout most frequently occurs when performing Transaction checks. Uptime.com’s transaction checks have a max runtime of 60 seconds. If the checks runs longer it will be considered down. The most common reasons for this error message occurring are:
- The Timeout (secs) setting has been adjusted in the Advanced options and is too low for the Transaction check, so the steps cannot be completed in the given time.
- There is an excessive number of commands or validations in the Transaction check, so that it cannot complete the full transaction in the default of 60 seconds.
- Uptime’s probe servers encounter an unresponsive endpoint at one of the steps, such as an unresponsive site or a network issue that fails to load the page as expected.
When receiving a Global Script Execution Timeout error, we recommend using Root Cause Analysis to identify the specific step where the failure occurred. To view more information about using Root Cause Analysis, please refer to the appropriate documentation here. In addition, reviewing the image and console log that has been provided in the alert may assist you in troubleshooting the issue at hand.
HTTP(S) checks can also timeout if the performance of the server is experiencing degraded performance. The Timeout for HTTP(S) checks defaults to 40 seconds. If the Global Script Execution Timeout error occurs for this check, it is recommended to check server logs and performance for excessive latency.