You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We enjoy using the maxLostRecordsPercentage option in the safetyChecks. But sometimes the crawler fails to fetch one or more of our pages, resulting in a lost amount of records that stays below this threshold. The crawler then happily proceeds publishing the incomplete index.
Would love to be able to be looser about losing records to allow for changes in our content, but have a zero-tolerance for failed urls.
Describe the solution
Would love to be able to set something like a maxFailedUrls in the safetyChecks which blocks the crawler from publishing the index if any amount of urls failed to be crawled.
Additionally, it would be helpful if the crawler could retry fetching urls, with some backoff pattern.
Alternatives you've considered
The text was updated successfully, but these errors were encountered:
Describe the problem
We enjoy using the
maxLostRecordsPercentage
option in thesafetyChecks
. But sometimes the crawler fails to fetch one or more of our pages, resulting in a lost amount of records that stays below this threshold. The crawler then happily proceeds publishing the incomplete index.Would love to be able to be looser about losing records to allow for changes in our content, but have a zero-tolerance for failed urls.
Describe the solution
Would love to be able to set something like a
maxFailedUrls
in the safetyChecks which blocks the crawler from publishing the index if any amount of urls failed to be crawled.Additionally, it would be helpful if the crawler could retry fetching urls, with some backoff pattern.
Alternatives you've considered
The text was updated successfully, but these errors were encountered: