...
The Browser Result Details view contains information about check results in a number of charts, graphs and tables. This view is most useful for analyzing browser results for scenarios. The type of information displayed in the view depends on the check type. For a scenario, several aspects of the check are shown in different areas.
...
There are a number of error types that can be reported for a step.
Job Timeout
...
A job timeout error means that the scenario step running time has exceeded the allowed time.
...
Causes
The job timeout error can mean that a single scenario step runs for too long, due to a coding problem, or some other reason.
There can also be connection issues or very slow - or none at all - responses from the target server.
...
Request Timeout
If a URL in your scenario does not return a response within X seconds after the DOM complete is sent, you will see an error informing you that the URL timed out:
...
The number of seconds which the check will wait for request resolutions after DOM complete can be configured in the Edit Check settings:
...
Altering the request activity timeout can help in situations where a certain URL is simply taking a long time to return a response. However, if the URL is not returning a response at all, the URL will fail regardless of the value you enter in the Request Activity Timeout input above.
Redirect Loop
The Redirect Loop error typically indicates that the there isa circular redirection happening with the request.
Causes
The typical cause of this error is a page that redirects to another page which in turn (possibly via multiple other pages) redirects back to the original page.
Redirect loop errors can also occur when the page redirects to itself, possibly due to a programming error or misconfiguration of an
htaccessfile or the web server.Additionally, and more rarely, the error can be trigged if there is no actual loop, but there are too many HTTP redirects before a page is reached that does not also issue a redirect.
...