Versions Compared

Old Version 3

changes.mady.by.user Ricardo Fonseca

Saved on

compared with

New Version Current

changes.mady.by.user Pablo Bonilla

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



  • An HTTP 429 errors error occurs when too many requests have been sent to a content source in a given amount of time.
  • These errors may occur when requesting data from certain content sources such as Microsoft Cloud Services (Sharepoint, OneDrive, O365, Azure AD), Box, Elasticsearch and others.
  • The errors are retried automatically by Aspire and what Aspire does is waiting Aspire will retry the errors automatically and will wait a set amount of time before retrying again, based on the error response header, or if this header is not returned, on the configured parameters.
  • This is a mitigation strategy and not a final fix since, in the end, the underlying problem is that the content source is not able to respond to the requests fast enough and as a result, sometimes a new crawl will be necessary to pick up items that failed completely.
  • If HTTP 429 errors are happening too frequently, it might be worth it to place placing a throttling policy for the crawl, as described here.