{"version":"2.1.260","anchor":"unreadable-settings-error-now-covers-sandbox-settings-too-a","canonical_anchor":"unreadable-settings-error-now-covers-sandbox-settings-too-a","heading":"Unreadable-settings error now covers sandbox settings too, and points to \/status","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/unreadable-settings-error-now-covers-sandbox-settings-too-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Unreadable-settings error now covers sandbox settings too, and points to \/status\n\nUnreadable-settings warnings now cover sandbox settings and point to \/status.\n\nThe warning shown when a settings file has errors during a teleport\/cloud-session bundle now also covers sandbox settings, not just Read rules, and lists which specific settings files could not be read.\n\n- Area: Settings\n- Names: `\/status`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}