{"version":"2.1.281","anchor":"dir-sync-records-with-no-engine-no-longer-detected-as-the-le","canonical_anchor":"dir-sync-records-with-no-engine-no-longer-detected-as-the-le","heading":"Dir-sync records with no engine no longer detected as the legacy 'rows' engine","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-records-with-no-engine-no-longer-detected-as-the-le","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync records with no engine no longer detected as the legacy 'rows' engine\n\nDir-sync records with no engine are now simply reported as unreadable, not probed and called the old \"rows\" engine\n\n**Unclear.** The finding does not say what dir-sync records are or where the result appears.\n\n**What**\n\nA dir-sync record that does not name an engine is now always reported as unreadable. Before, Claude Code examined such a record and could report it as the unsupported engine \"rows\".\n\n**Why**\n\nRecords like this now get one plain result instead of being labelled as an older format.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}