Deployment Monitoring Errors and Actions

Modified on Tue, 22 Aug 2023 at 09:36 AM

Schema App's Deployment Monitoring feature verifies that the correct Schema Markup is deploying to the intended pages. It also assesses whether web crawlers can read the deployed markup. If any disruptions or discrepancies are found, a notification will be emailed to the account's designated Customer Success Manager.

This article defines the error messages and describes courses of action for resolving each.


Error Messages

Markup from this source is missing

This error message is triggered when Deployment Monitoring finds Schema Markup on a page but it isn't from the source named in the source column.

Expected sources can be:

  • Highlighter templates
  • Editor
  • Shopify
  • BigCommerce
  • Merchant Center
  • WordPress

No markup was found

This error message is triggered when Deployment Monitoring finds no schema markup on a page. This means no JSON-LD is present on the page from any source. 

Common Issues and Troubleshooting

1. URL Change

  • Problem: URL has been redirected to another URL
  • Solution - Editor:
    1. In Schema App, navigate to Editor > Data Items
    2. Search for data items with the affected URL
    3. Select all URIs that are related to that data item and bulk change them to the new redirected URL.
  • Solution - Highlighter:
    1. Locate the Highlighter template where the issue is occurring. 
    2. Edit the template. 
    3. Go to Step 3 and replace the URL if it is used as a test URL. 
    4. If it is not in Step 3, modify the template, then click save to trigger it to redeploy to the listed URLs.
    5. If deploying with the Crawler, click "Start New Crawl" from the Highlighter landing page

2. URL has been Deleted from Website

  • Problem: The client has removed the URL from the website
  • Solution - Editor:
    1. In Schema App, navigate to Editor > Data Items
    2. Search for data items with the affected URL
    3. Select all URIs that are related to that data item and bulk delete.
  • Solution - Highlighter: 
    1. Locate the template where the issue is occurring. 
    2. Go to step 3 and delete the URL if it is used as a test URL. 
    3. Replace it with a URL that fits the template.
    4. If it is not in step 3, make a save to the template which will trigger it to add in a new list of URLs.
    5. If deploying with the Crawler, click "Start New Crawl" from the Highlighter landing page.

3. Integration/Scripts have been Removed

  • Problem: Schema App's scripts have been removed from the site, or the existing plugin has been uninstalled.
  • Solution - Scripts:
    1. Navigate to a URL where Schema App markup is expected
    2. In Dev Tools > Elements, search for "highlight". If Schema App's scripts do not appear, they've likely been removed
    3. In Dev Tools > Console, search for "schema_highlighter" to verify whether scripts exist and are recognized.
  • Solution - Plugins:
    1. Login to your CMS
    2. Confirm whether the relevant Schema App plugin is installed

4. Drupal Deployment URL Check

  • Problem: If using the Drupal deployment method and markup from the Editor is not being shown on page, it's possible the URL is different from what you see.
  • Solution: See Troubleshooting: Drupal front page markup

How to Prevent False Alerts

1. Exclude URL Patterns from Deployment Monitoring

In some cases, certain URLs should always be omitted from Deployment Monitoring because they are known to trigger false alerts. This can be done through the following steps:

  1. Click on your user name and selecting "Settings"
  2. Go to the "Project Settings" tab
  3. List individual URLs or URL Patterns that should be excluded from the report. 
  4. Click "Save".

2. Exclude Project from Error Monitoring

In some cases, you may have:

  • Projects created for testing environments which do not require Deployment Monitoring to run.
  • Clients who do not want Deployment Monitoring to run on their site

You can exclude an entire project from Deployment Monitoring, through the following steps:

  1. Click on your user name and selecting "Settings"
  2. Go to the "Project Settings" tab
  3. Select "URL Pattern"
  4. Enter: /**
  5. Click "Save"


Note: You may receive notifications for URLs that have been excluded from Highlighter templates if the excluded URLs have been added to the pageset in Step 3. Make sure any excluded URLs are added to "Exclude URL Patterns From Deployment Monitoring".

Error Codes and Mitigations

The following is a list of HTTP status codes, what they indicate, possible diagnoses and suggested actions. 

CodeDescriptionExplanationPossible diagnosisClient Suggestion
Contact own ITTake action if repeatedCheck if page existsContact CSM
100ContinueThe 100 Continue status code means that the initial part of the request has been received by the server and that the client should proceed with the request or ignore the response if the request has already finished.None
101Switching ProtocolsThe requester has asked the server to switch protocols and the server has agreed to do so.None
102Processing (WebDAV; RFC 2518)A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. [3] This prevents the client from timing out and assuming the request was lost. The status code is deprecated.[4]None
103Early Hints (RFC 8297)Used to return some response headers before final HTTP message.[5]None
200OKStandard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.None
201CreatedThe request has been fulfilled, resulting in the creation of a new resource.[6]Unknown server issue / configuration✔️
202AcceptedThe request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.Unknown server issue / configuration✔️✔️✔️
203Non-Authoritative Information (since HTTP/1.1)The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.[7][8]Unknown server issue / configuration✔️✔️✔️
204No ContentThe server successfully processed the request, and is not returning any content.Unknown server issue or page does not exist / page contains no content.✔️✔️✔️
205Reset ContentThe server successfully processed the request, asks that the requester reset its document view, and is not returning any content.Unknown server issue / configuration✔️✔️✔️
206Partial ContentThe server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.Unknown server issue / configuration✔️✔️✔️
207Multi-Status (WebDAV; RFC 4918)The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.[9]N/A✔️✔️
208Already Reported (WebDAV; RFC 5842)The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.N/A✔️✔️
226IM Used (RFC 3229)The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.[10]N/A✔️✔️
300Multiple ChoicesIndicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.Page target URL incorrect / Server configuration✔️✔️
301Moved PermanentlyThis and all future requests should be directed to the given URI.Page target URL incorrect / Server configuration✔️✔️
302Found (Previously "Moved temporarily")Tells the client to look at (browse to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect with the same method (the original describing phrase was "Moved Temporarily"),[12] but popular browsers implemented 302 redirects by changing the method to GET. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[11]Page target URL incorrect / Server configuration✔️✔️
303See Other (since HTTP/1.1)The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.Page target URL incorrect / Server configuration✔️✔️
304Not ModifiedIndicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.Page target URL incorrect / Server configuration✔️✔️
305Use Proxy (since HTTP/1.1)The requested resource is available only through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not obey this status code.[13]Page target URL incorrect / Server configuration✔️✔️
307Temporary Redirect (since HTTP/1.1)In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.Page target URL incorrect / Server configuration✔️✔️
308Permanent RedirectThis and all future requests should be directed to the given URI. 308 parallel the behaviour of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.Page target URL incorrect / Server configuration✔️✔️
400Bad RequestThe server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).Server issue or crawler issue✔️✔️✔️
401UnauthorizedSimilar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means "unauthorised", the user does not have valid authentication credentials for the target resource.Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.[citation needed]Login required to access page✔️✔️
402Payment RequiredReserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler,[14] but that has not yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.[15] Sipgate uses this code if an account does not have sufficient funds to start a call.[16] Shopify uses this code when the store has not paid their fees and is temporarily disabled.[17] Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.[18]Payment required to access page✔️✔️
403ForbiddenThe request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication. The request should not be repeated.Page target URL incorrect / Server configuration✔️✔️
404Not FoundThe requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.Page target URL incorrect / Server configuration✔️✔️
405Method Not AllowedA request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.Unknown server issue / configuration✔️✔️✔️
406Not AcceptableThe requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.Unknown server issue / configuration✔️✔️✔️
407Proxy Authentication RequiredThe client must first authenticate itself with the proxy.Login required to access page✔️✔️
408Request TimeoutThe server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."Unknown server issue / configuration✔️✔️✔️
409ConflictIndicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.Unknown server issue / configuration✔️✔️✔️
410GoneIndicates that the resource requested was previously in use but is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.Unknown server issue or page does not exist / page contains no content.✔️✔️✔️
411Length RequiredThe request did not specify the length of its content, which is required by the requested resource.Bad crawler request✔️✔️
412Precondition FailedThe server does not meet one of the preconditions that the requester put on the request header fields.Bad crawler request✔️✔️
413Payload Too LargeThe request is larger than the server is willing or able to process. Previously called "Request Entity Too Large" in RFC 2616.[19]Unknown server issue / configuration✔️✔️✔️
414URI Too LongThe URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously in RFC 2616.[20]Page target URL incorrect / Server configuration✔️✔️
415Unsupported Media TypeThe request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.Unknown server issue / configuration✔️✔️✔️
416Range Not SatisfiableThe client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously RFC 2616.[21]Unknown server issue / configuration✔️✔️✔️
417Expectation FailedThe server cannot meet the requirements of the Expect request-header field.[22]Unknown server issue / configuration✔️✔️✔️
418I'm a teapot (RFC 2324, RFC 7168)This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[23] This HTTP status is used as an Easter egg in some websites, such as's "I'm a teapot" easter egg.[24][25][26] Sometimes, this status code is also used as a response to a blocked request, instead of the more appropriate 403 Forbidden.[27][28]Unknown server issue / configuration✔️✔️✔️
419Page ExpiredUsed by the Laravel Framework when a CSRF Token is missing or expired.Login required to access page✔️✔️
421Misdirected RequestThe request was directed at a server that is not able to produce a response (for example because of connection reuse).Unknown server issue / configuration✔️✔️✔️
422Unprocessable EntityThe request was well-formed but was unable to be followed due to semantic errors.[9]Unknown server issue / configuration✔️✔️✔️
423Locked (WebDAV; RFC 4918)The resource that is being accessed is locked.[9]Retry later✔️✔️
424Failed Dependency (WebDAV; RFC 4918)The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).[9]Retry later✔️✔️
425Too Early (RFC 8470)Indicates that the server is unwilling to risk processing a request that might be replayed.Retry later✔️✔️
426Upgrade RequiredThe client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.Bad crawler request✔️✔️
428Precondition Required (RFC 6585)The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.[29]Retry later✔️✔️
429Too Many Requests (RFC 6585)The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.[29]Retry later✔️✔️
430Request Header Fields Too LargeUsed by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.[36]Retry later✔️✔️
431Request Header Fields Too Large (RFC 6585)The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.[29]Bad crawler request✔️✔️
440Login Time-outThe client's session has expired and must log in again.[43]Login required to access page✔️✔️
444No ResponseUsed internally[50] to instruct the server to return no information to the client and close the connection immediately.Unknown server issue / configuration✔️✔️✔️
449Retry WithThe server cannot honour the request because the user has not provided the required information.[44]Login required to access page✔️✔️
450Blocked by Windows Parental ControlsThe Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.[37]Unknown server issue / configuration✔️✔️✔️
451Unavailable For Legal Reasons (RFC 7725)A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.[30]Page target URL incorrect / Server configuration✔️✔️
460Error 460Client closed the connection with the load balancer before the idle timeout period elapsed. Typically when client timeout is sooner than the Elastic Load Balancer's timeout.[55]Unknown server issue / configuration✔️✔️✔️
463Error 463The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.[55]Unknown server issue / configuration✔️✔️✔️
464Error 464Incompatible protocol versions between Client and Origin server.[55]Unknown server issue / configuration✔️✔️✔️
494Request header too largeClient sent too large request or too long header line.Bad crawler request✔️✔️
495SSL Certificate ErrorAn expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.Bad crawler request✔️✔️
496SSL Certificate RequiredAn expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.Bad crawler request✔️✔️
497HTTP Request Sent to HTTPS PortAn expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.Bad crawler request✔️✔️
498Invalid TokenReturned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.[38]Login required to access page✔️✔️
499Client Closed RequestUsed when the client has closed the request before the server could send a response.Bad crawler request✔️✔️
499Token RequiredReturned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.[38]Login required to access page✔️✔️
500Internal Server ErrorA generic error message, given when an unexpected condition was encountered and no more specific message is suitable.Unknown server issue / configuration✔️
501Not ImplementedThe server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).Unknown server issue / configuration✔️✔️✔️
502Bad GatewayThe server was acting as a gateway or proxy and received an invalid response from the upstream server.Unknown server issue / configuration✔️
503Service UnavailableThe server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[31]Unknown server issue / configuration✔️✔️✔️
504Gateway TimeoutThe server was acting as a gateway or proxy and did not receive a timely response from the upstream server.Unknown server issue / configuration✔️
505HTTP Version Not SupportedThe server does not support the HTTP version used in the request.Unknown server issue / configuration✔️✔️✔️
>506Variant Also Negotiates (RFC 2295)Transparent content negotiation for the request results in a circular reference.[32]Unknown server issue / configuration✔️✔️✔️
>507Insufficient Storage (WebDAV; RFC 4918)The server is unable to store the representation needed to complete the request.[9]Unknown server issue / configuration✔️✔️✔️
>508Loop Detected (WebDAV; RFC 5842)The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).Unknown server issue / configuration✔️✔️✔️
>509Bandwidth Limit ExceededThe server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.[39]Retry later✔️✔️
>510Not Extended (RFC 2774)Further extensions to the request are required for the server to fulfil it.[33]Unknown server issue / configuration✔️✔️✔️
511Network Authentication Required (RFC 6585)The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).[29]Login required to access page✔️✔️
520Web Server Returned an Unknown ErrorThe origin server returned an empty, unknown, or unexpected response to Cloudflare.[52]Unknown server issue / configuration✔️✔️✔️
521Web Server Is DownThe origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses.Unknown server issue / configuration✔️✔️✔️
522Connection Timed OutCloudflare timed out contacting the origin server.Unknown server issue / configuration✔️✔️✔️
523Origin Is UnreachableCloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect or missing.Unknown server issue / configuration✔️✔️✔️
524A Timeout OccurredCloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.Unknown server issue / configuration✔️✔️✔️
525SSL Handshake FailedCloudflare could not negotiate a SSL/TLS handshake with the origin server.Unknown server issue / configuration✔️✔️✔️
526Invalid SSL CertificateCloudflare could not validate the SSL certificate on the origin web server. Also used by Cloud Foundry's gorouter.Unknown server issue / configuration✔️✔️✔️
527Railgun ErrorError 527 indicates an interrupted connection between Cloudflare and the origin server's Railgun server.[53]Unknown server issue / configuration✔️✔️✔️
529Site is overloadedUsed by Qualys in the SSLLabs server testing API to signal that the site can't process the request.[40]Retry later✔️✔️
530Error 530Error 530 is returned along with a 1xxx error.[54]Unknown server issue / configuration✔️✔️✔️
561UnauthorizedAn error around authentication returned by a server registered with a load balancer. You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.[55]Login required to access page✔️✔️
598(Informal convention) Network read timeout errorUsed by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.[42]Unknown server issue / configuration✔️✔️✔️
599Network Connect Timeout ErrorAn error used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.Unknown server issue / configuration✔️✔️✔️
999Request DeniedWhen sending an HTTP GET or HEAD request to LinkedIn for a specific profile, such as the page for a company or an individual, the 999 Request Denied status code response is returned based on, among other things, the user agent.Login required to access page✔️✔️

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article