# MaxLinkChanges

The maximum number of links that can no longer appear on a page, compared to the last time the page was synchronized, for the connector to delete unreachable pages that it has seen before.

You might use this parameter to prevent the connector sending ingest-deletes when pages fail to load correctly. For example, if the links on a page are generated by a script that does not complete in a reasonable amount of time, the connector might send ingest-deletes for pages and other resources that it has seen before, because it can no longer reach them.

If a page is synchronized and more than the specified number of links have been deleted, page processing returns an error, all links are assumed to be unchanged, and the connector attempts to process the page again during the next synchronize cycle. The connector attempts to process the linked pages that were seen during the previous synchronize cycle, so if any have been deleted then the connector will receive HTTP 404 (not found) errors from the server and send ingest-deletes for the relevant pages.

NOTE: When you set both this parameter and MaxLinkChangePercentage, a page only has to meet one of the limits to be processed. For example, if the connector finds 10 out of 40 links are missing when you set `MaxLinkChanges=5` and `MaxLinkChangePercentage=25`, the connector deletes the unreachable pages.

Type: | Integer
Default: | 0 (no limit)
Required: | No
Configuration Section: | TaskName or FetchTasks
Example: | `MaxLinkChanges=10`
See Also: | MaxLinkChangePercentage

_FT_HTML5_bannerTitle.htm