Failed downloads screen
Inventory > Failed downloads lists every URL Silktide could not fetch the last time it tried, together with the reason.
A page that could not be fetched cannot be tested, so it contributes nothing to your scores. Without this screen a failure is invisible: a page Silktide could not reach and a page that no longer exists look identical if all you can compare is page counts between tests.
What the columns tell you
- URL - the address Silktide requested.
- Status - why it failed, as a label such as Removed, Rate limited, Timeout, or Blocked. Filter by status to see one kind of failure at a time.
- HTTP code - what the server answered with, where it answered at all.
- Error message - extra detail, when we have something more specific to say.
- Downloaded - when the attempt was made.
Common statuses
- Removed - the URL returned
404. Usually expected: the page has gone, and Silktide will stop testing it. - Rate limited - the website refused to serve the page because Silktide was asking too quickly. See Rate limiting and retries.
- Timeout - the page did not respond in time. Advanced settings controls how long Silktide waits.
- Blocked - a firewall, , or bot protection refused the request. See What IP address and user agent does Silktide use?.
- Failed authentication - Silktide could not sign in, so it could not reach content behind the login.
- Not testable - the URL returned something Silktide cannot test, such as an image or a calendar file.
- Failed - something went wrong on Silktide's side, for example the page could not be rendered in a browser. The error message says what happened.
Each URL shows its latest attempt
A full test of the website, or of some of its sections, starts this list afresh. While it is running the list is incomplete and will grow.
Retesting one page or a few URLs updates only those URLs. A URL that now works leaves the list, a URL that fails again shows its new reason, and every other URL keeps the reason from when it was last tried. Downloaded says when that was.
It is not a history: you cannot use it to compare which pages failed last week against this week.
Related
- Understanding inventory coverage - why what Silktide found may differ from a list.
- Rate limiting and retries - what happens when a website limits how fast it can be tested.
- Why did my score change when the website did not? - failed downloads are one of the causes.