Troubleshooting

A test is marked as Aborted if it did not complete successfully or was stopped by the user. If the test was aborted by the system, check that the tunnel is configured correctly. For details see Configuring a Tunnel

If the tunnel is configured correctly, you should look at test details and may need to contact support. For details see Viewing or Copying Test Details.

Following are common server errors:

• 401 (Unauthorized) – Autonomous does not have permission to access this page. This can occur if the page is password-protected, requires credentials, or you need to accept cookies before the test opens. To resolve this issue, you can add basic authentication or a customized pre-test. For details, see Flow to Run Before Steps.

• Error 403 (Forbidden) – The server is blocking access. To resolve this issue, add the website to a whitelist (for assistance contact support), or access the website using a tunnel. For details, see Configuring a Tunnel.

• Error 404 (Not found) – the URL is not currently available, try again later. If this page no longer exists, you should remove it from the sitemap or the list of URLs.

• Error 429 (Too many requests) – The server is blocking access. To resolve this issue, add the website to a whitelist (for assistance contact support), or access the website using a tunnel. For details, see Configuring a Tunnel.

• 500 (Internal Server Error) – Autonomous is unable to establish a connection with the server. To confirm that the server is available, try accessing the URL with your browser.

• 503 (Service Unavailable) – Autonomous is unable to establish a connection with the server, the server may be temporarily overloaded or down for maintenance. To confirm that the server is available, try accessing the URL with your browser.

Problem:

Autonomous is unable to find the sitemap, or there is no sitemap file.

Solution:

By default, Autonomous looks for a sitemap file in the root directory, the file must be named sitemap.xml or listed in the robots.txt file. This error appears if Autonomous is unable to find a sitemap file. To resolve this problem try one of the following:

• Add a sitemap file named sitemap.xml to the root directory.

• If there is a sitemap file with a different name or in a different location, when creating the full website test, enter the full path to the sitemap file instead of the root directory.

• If there is no sitemap file and you are unable to create one, create a URL list test instead of a Full Website Test. See URL List Test

Problem:

The domain test timed out

Solution:

This could be caused by a network issue, try again later.

Problem:

An error message appears that not all screens were included in the test or one or more directory was excluded from the test.

Solution:

There is a limit on the number of screens that can be included in a single test. The maximum number is based in your Autonomous plan. If your sitemap includes too many URLs, try one of the following:

• Manually select URLs that should be excluded from the test. For details, see Excluding or Adding URLs.

• Create a separate test for each sub-directory

• Contact Support to increase the number of URLs allowed in your plan

This error is caused because the server timed out before it was able to process the complete sitemap, this is normally because the sitemap is extremely large.

If the sitemap includes multiple nested sitemaps, you should create a separate full website test for each nested sitemap. When you create the test, instead of entering the URL of your website, enter the full path to a nested sitemap.

Problem:

An "Unknown Error" occurred when creating a test for a sub-directory (for example http://www.mynewssite.com/sport)

Solution:

When creating a test for a sub-directory, Autonomous uses the sitemap in the root folder to identify screens in the sub-directory. If the sub-directory has a separate sitemap, when you create the test, enter the full path to the sitemap for the sub-directory.