{"version":"2.1.222","anchor":"plugin-sync-list-failures-carry-http-status-and-403-is-not-r","canonical_anchor":"plugin-sync-list-failures-carry-http-status-and-403-is-not-r","heading":"Plugin sync list failures carry HTTP status and 403 is not retried","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/plugin-sync-list-failures-carry-http-status-and-403-is-not-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Plugin sync list failures carry HTTP status and 403 is not retried\n\nPlugin syncing fails fast on a forbidden response and tells you the HTTP status.\n\n**What**\n\nA forbidden response when listing plugins fails fast instead of burning through the retry schedule, and the failure now reports which HTTP status caused it.\n\n**Details**\n\n- The list-plugins error envelope returns `status` along with `success: !1`, and the status is included in the `plugins_sync_list_error` warning\n- The retry wrapper returns immediately when `t.status === 403` rather than sleeping and retrying\n- A sibling retry helper was simplified to test `t.ok` only\n\n**Evidence**\n\n`plugins_sync_list_error`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}