{"version":"2.1.305","anchor":"plugin-directory-fetch-records-latermayhelp-service-delay","canonical_anchor":"plugin-directory-fetch-records-latermayhelp-service-delay","heading":"Plugin directory failures record when they happened and whether retrying may help","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-directory-fetch-records-latermayhelp-service-delay","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Plugin directory failures record when they happened and whether retrying may help\n\nFailed plugin directory fetches now record time, reason and service delay, say whether retrying may help, and flag plugins that cannot be installed\n\n**What**\n\nThe plugin Directory is the online catalog Claude Code reads to find plugins (add-ons).\n\n- A failed or backed-off fetch now carries `laterMayHelp`, saying a later retry might work.\n\n- Failed fetches record `failedAt` and `serviceDelayMs`. A new helper returns the last failure with `closesAt`, `reason`, `failedAt` and `serviceDelayMs`, and returns nothing once its window has expired.\n\n- Successful fetches are marked with `walked` and `walkStarted`.\n\n- Loading returns `notInstallable` for each plugin that cannot be installed.\n\n- When only the copy saved on your machine answered, loading returns an error: \"only the list saved on this machine answered, not the Directory itself\". Before, only a marketplace switch required a fresh read.\n\n**Why**\n\nPlugin screens can tell you whether trying again is worthwhile and why a plugin cannot be installed, instead of silently using a stale saved list.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}