{"version":"2.1.261","anchor":"new-diagnostics-for-org-managed-hook-restrictions-on-synced","canonical_anchor":"new-diagnostics-for-org-managed-hook-restrictions-on-synced","heading":"New diagnostics for org-managed hook restrictions on synced plugins","tier":"notice","area":"Plugin Management","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/new-diagnostics-for-org-managed-hook-restrictions-on-synced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### New diagnostics for org-managed hook restrictions on synced plugins\n\nNew diagnostics explain when org-managed hook restrictions or disabled settings are suppressing a synced plugin.\n\nTwo new plugin-issue diagnostics help explain org-managed hook behavior on synced plugins. `managed-hooks-restricted` reports when a plugin loads because it matches an org-mandated plugin by sync attribution, but its hooks are suppressed because `allowManagedHooksOnly` only runs hooks from the exact managed plugin@marketplace id. `managed-plugin-disabled-by-settings` reports when a locally-disabled copy of a plugin shadows what the org's managed settings expect to be running. Both include remediation text.\n\n- Area: Plugin Management\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}