Crawl Safeguard
January 31st 2025
To make sure crawls complete quickly and efficiently, we’ve improved visibility into what we’re crawling as we crawl, and added additional crawl safeguards to the Lumar Platform:
-
You can now see a summary of the count of URLs per status code in the last 5 minutes on the crawl progress screen.
-
You can also see a trend of the failure rate per 5 minutes for the last hour, with the overload percentage.
-
In the project settings, you can now set a threshold for the percentage of errors within a fixed timeframe, which will pause the crawl when the rate is exceeded. You’ll see a message on the crawl progress screen to explain that the crawl was paused due to errors, and receive an email so you can investigate and disable the overload protection if required.
Note that these settings are not enabled by default at this stage, but can be enabled for any new or existing crawls as required. We'll then look at adding the crawl safeguard settings by default for new projects in the future. In the meantime, you can enable the safeguard settings on the crawl progress screen, or in the Crawl Safeguard option in Advanced Settings in Step 4 of the crawl setup.
Protect Tests on Health Scores
January 20th 2025
To help you identify issues before new code is published, you can now create tests for health scores in Protect. This means you can now run health score tests on templates, or automatically stop builds if you integrate Protect with your CI/CD pipeline, to check for any site health degradation before changes go live.