{"version":"2.1.238","anchor":"clean-filter-reconciliation-is-timed-and-reported","canonical_anchor":"clean-filter-reconciliation-is-timed-and-reported","heading":"Clean-filter reconciliation is timed and reported","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/clean-filter-reconciliation-is-timed-and-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Clean-filter reconciliation is timed and reported\n\nThe change-detection scan can be cancelled and now reports how many files it checked and how long it took.\n\n**What**\n\nThe scan that decides which files changed now consults git clean-filter blob ids, can be cancelled part-way, and reports how many files it asked about, how many settled, and how long it took.\n\n**Details**\n\n- A file previously marked changed can be reclassified as unchanged once the filter answers.\n- Two copies of a file are now also considered in agreement when their git blob id matches and etag and mode still line up, not only when their sha256 matches.\n- There is a cap on how many decisions a worker will defer.\n\n**Evidence**\n\n`filter_settled`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}