Core Assurance Failure Codes
When a run fails, the Test Results page shows the reason in the Error Detail column, and the Test Details page shows the reason in the Error column. Each reason corresponds to one of the failure codes in the following sections. Some codes apply only when you set the related optional value in the test profile, such as Max Response Time (ms).
To see the codes for a test type while you create or edit a test profile, click Show Possible Failure Codes on the Pass Criteria tab.
Failure codes for more than one test type
The following codes can occur for more than one test type.
|
Failure code |
When it occurs |
|---|---|
|
|
The same test was already running on the endpoint when the next run was due. Applies to every test type. |
|
|
The endpoint was already running the maximum number of tests allowed at the same time. Applies to every test type. |
|
|
The target host name could not be resolved to an IP address. Applies to every test type except DNS Lookup. |
Ping failure codes
For the fields and pass criteria of a Ping test, see Ping Tests.
|
Failure code |
When it occurs |
|---|---|
|
|
The network reports that the destination is unreachable. |
|
|
No ICMP reply arrived before the timeout. |
|
|
The round-trip time was longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value. |
TCP Port failure codes
For the fields and pass criteria of a TCP Port test, see TCP Port Tests.
|
Failure code |
When it occurs |
|---|---|
|
|
The network is unreachable, or there is no route to the host. |
|
|
The host refused the connection because nothing is listening on the port. |
|
|
The TCP connection did not complete within the timeout. |
|
|
Another connection error occurred. For example, a firewall dropped the connection without a response. |
|
|
The connection succeeded but took longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value. |
HTTP URL failure codes
For the fields and pass criteria of an HTTP URL test, see HTTP URL Tests.
|
Failure code |
When it occurs |
|---|---|
|
|
The TCP connection failed because it was refused, the host was unreachable, or the connection timed out. |
|
|
The TLS (Transport Layer Security) handshake failed, or the server certificate is not valid. |
|
|
A complete response did not arrive within the timeout. |
|
|
The status code did not match Expected Status Code. For example, the server returned 503 when the profile expects 200 to 299. |
|
|
The server sent the request through more redirects than the test allows. The redirect limit is fixed and cannot be changed in the profile. |
|
|
An HTTP/2 framing or protocol error occurred. |
|
|
The connection dropped during the request or the response. |
|
|
The response took longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value. |
DNS Lookup failure codes
For the fields and pass criteria of a DNS Lookup test, see DNS Lookup Tests.
|
Failure code |
When it occurs |
|---|---|
|
|
The DNS server did not respond within the timeout. |
|
|
The domain name does not exist. |
|
|
The query succeeded, but no records of the requested type were returned. |
|
|
No response arrived before the query timeout. |
|
|
Records were returned, but the records do not satisfy the comparison with Expected Resolved IPs (optional). |
|
|
The DNS server returned a server failure. |
|
|
The DNS server refused the query, usually because of a policy or access list. |
Traceroute failure codes
For the fields and pass criteria of a traceroute test, see Traceroute Tests.
Both traceroute types share the following codes. The last two codes in the table apply only to Traceroute TCP.
|
Failure code |
When it occurs |
|---|---|
|
|
No hops were discovered, and the target was not reached. |
|
|
The test reached Max Hops without confirming the target. |
|
|
More hops in a row were silent than Hop Gap Limit allows, so the test stopped. |
|
|
The whole run took longer than Path Timeout (ms). |
|
|
The target was reached, but the end-to-end round-trip time was longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value. |
|
|
Traceroute TCP only. The target reported that the port is unreachable, but the profile requires the port to be open. |
|
|
Traceroute TCP only. The target sent no response at all, and Requires Target Reached is set to Yes. |