📘 This article provides descriptions of the reasons why SpeedWorkers could not cache a page. SpeedWorkers is part of Botify's Activation Suite, available as an option with a Botify Pro or Enterprise plan.
Overview
There are many reasons why SpeedWorkers is not able to cache a page. Pages not cached during the selected period are included in the "Total Fetched Pages by Date" chart on the Cache Refreshes tab of the Inventory Monitoring page. Individual pages not cached are identified by drilling through the Not Cached metric in that chart or by navigating directly to the SpeedWorkers URL Explorer.
Not Cached Reasons
The following are reasons why a page was not cached in SpeedWorkers:
Reason | Description |
bad token | The request token is not valid or does not have the proper rights. |
cached | This value is displayed in the SpeedWorkers URL Explorer "Not Cached Reason" column for pages that were cached. |
configuration | The page should not be delivered based on the current configuration settings. |
custom response | Live JavaScript returned a custom error code. |
no data | SpeedWorkers never attempted to add the page to the inventory; therefore, there is no "not cached" value. |
internal error | SpeedWorkers encountered an error (e.g., internal error, timeout, server overloaded). |
origin server error | The origin server returned an error when caching, fetching, or rendering the page. |
request origin timeout | The origin server timed out. |
quality controls failed | There was a failure of a defined quality control rule. |
invalid request | The incoming request contains bad parameters. |
delivery stopped | The delivery of pages stopped based on the current configuration settings. |
ip filtered | The page request was blocked because the IP doesn't belong to a search engine, hasn't been resolved yet, or has been explicitly blocked in the configuration. |
js code error | SpeedWorkers encountered an error while executing JavaScript on the page. |
js redirect not enabled | The page has not been delivered because it is a JavaScript redirect (309 HTTP code), and no configuration has been set to return them as real redirects. |
not html | The page does not have a text/html content-type in its header. Note: A 302 does not have content-type, but is deliverable. |
js redirect same url | The page has not been delivered because the JavaScript redirect location is the same as the requested URL. |
last refresh 4xx | A 4XX response (except 404) was returned during the last refresh. |
last refresh 5xx | A 5XX response was returned during the last refresh. |
out of scope | The page requested is on a domain that is out of scope and is, therefore, not allowed. |
throttled | SpeedWorkers may temporarily limit the number of requests allowed (i.e., return a 429 HTTP code) within a period when a bot performs too many requests. |
unsupported method | Botify only accepts HEAD and GET methods. |
websocket | Botify does not accept WebSockets. |