{"version":"2.1.229","anchor":"plugin-failures-caused-by-an-un-run-command-are-reported-as-","canonical_anchor":"plugin-failures-caused-by-an-un-run-command-are-reported-as-","heading":"Plugin failures caused by an un-run command are reported as policy errors","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/plugin-failures-caused-by-an-un-run-command-are-reported-as-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Plugin failures caused by an un-run command are reported as policy errors\n\nCertain plugin failures are now labelled policy problems, changing how they're shown to you.\n\n**What**\n\nMessages such as a plugin's command not having been run, command-sourced plugins being disabled, and the feature not being supported on Windows yet are now classified as policy failures rather than unknown ones, which changes how they are surfaced.\n\n**Evidence**\n\n`Command-sourced plugins are disabled`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}