If you receive SpeedWorkers email alerts, use the following to help troubleshoot the issue.
Cache Alerts
Alert name | Description | Recommended action |
Too many errors during indexation - QualityCheckFailed | An increase in failed quality controls on cached URLs, regardless of whether bots requested the URLs. These failures happen when there is a rendering error or an HTML change that differs from the settings’ logic. | The Botify team will investigate and determine the appropriate resolution. For example, if a change to the website causes the quality control to fail, you will share the change details, and Botify can update the quality control. |
Too many errors during indexation - NotHtml, Websocket
| An increase in URLs in the inventory that do not have content at the origin. | Following a discussion about the current site expectations, Botify could block these URLs from the cache, but these URLs need to be managed on your website. |
Too many errors during indexation - LastRefresh4XX, LastRefresh5XX | An increase in URLs in the inventory that served a 4XX or 5XX HTTP status code. | Depending on the specific code, this warrants investigation and action on your website. |
Too many errors during indexation - RedirectLoop, InvalidRedirect
| An increase in redirect errors in the inventory. | This warrants investigation and action on your website.
|
Too many stale or expired pages in inventory
| A bottleneck where SpeedWorkers cannot refresh the volume of URLs in the cache at the current frequency and crawl rate. | This can be corrected by modifying the inventory scope, reducing cache behavior refresh frequency, or increasing SpeedWorkers’ crawl rate. Botify can assist with a strategy to reduce staleness and expiration. |
Delivery Alerts
Alert name | Description | Recommended action |
Volume of delivered pages drop | A drop in URL delivery to bots, which typically occurs when there is an increase in delivery errors (like the errors listed above) or a sudden increase in new URLs added to the inventory that have not been cached.
| In this instance, the Botify team will investigate. Refer to SpeedWorkers Use Cases for Low Refresh Efficiency. |
Delivery requests drop | A connection issue between the origin CDN and the SpeedWorkers cache. | This warrants an investigation into CDN routing logic and security settings. |
Delivery QC failure | An increase in URLs requested by bots that are not fully rendering content, or there has been an HTML change that differs from the logic in SpeedWorker’s quality controls. | SpeedWorkers will revert bot traffic to the origin CDN to avoid serving errors to search engines while the Botify team modifies the rendering rules or updates the quality control criteria. |
Too many Control Center test failures | Botify runs automated tests on specific pages in the SpeedWorkers Control Center section to monitor the health of important pages and page types. This alert will trigger if there is a routing error or if the page no longer exists.
| If the page no longer exists, remove the URL and consider replacing it with a new one, if appropriate. If there is a routing issue, investigate with the CDN team. Refer to |