{"version":"2.1.281","anchor":"fix-in-the-acked-ancestor-check-picking-the-wrong-file-set","canonical_anchor":"fix-in-the-acked-ancestor-check-picking-the-wrong-file-set","heading":"Fix in the acked-ancestor check picking the wrong file set","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/fix-in-the-acked-ancestor-check-picking-the-wrong-file-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Fix in the acked-ancestor check picking the wrong file set\n\nA check for acknowledged ancestors now returns the files of the entry it matched instead of the wrong set\n\n**Unclear.** The finding does not say which feature uses this check or what a wrong result caused.\n\n**What**\n\nA check that looks for an acknowledged earlier entry was using the wrong values inside its loop. It now tests each entry it goes through and returns that entry's files and left-out list. If nothing matches, it falls back to a default.\n\n**Why**\n\nThe check could return the wrong set of files before. It now returns the files that belong to the entry it matched.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}