{"version":"2.1.281","anchor":"host-config-unreadable-cause-no-longer-treated-like-other-ha","canonical_anchor":"host-config-unreadable-cause-no-longer-treated-like-other-ha","heading":"host_config unreadable cause no longer treated like other hard causes","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/host-config-unreadable-cause-no-longer-treated-like-other-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### host_config unreadable cause no longer treated like other hard causes\n\nAn unreadable result caused by host_config is now handled like the \"other\" cause in a sync verdict check\n\n**Unclear.** The finding does not say what is being synced or what a false result from this check leads to.\n\n**What**\n\nA check that judges a sync result now returns false when the result is \"unreadable\" and the cause is `host_config`, the same way it already did for the cause \"other\".\n\n**Why**\n\nAn unreadable `host_config` is no longer treated the same as the remaining unreadable causes in this check.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}