{"version":"2.1.273","anchor":"catalog-fetch-retry-state-now-carries-explicit-disposition-i","canonical_anchor":"catalog-fetch-retry-state-now-carries-explicit-disposition-i","heading":"Catalog fetch-retry state now carries explicit disposition instead of a boolean","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/catalog-fetch-retry-state-now-carries-explicit-disposition-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Catalog fetch-retry state now carries explicit disposition instead of a boolean\n\nModel-catalog fetch retry logic now uses named outcomes instead of a true\/false flag\n\n**What**\n\nThe internal function that decides what to do after fetching the model catalog fails or succeeds now takes one of three explicit outcomes \u2014 `retry_soon`, `back_off`, or `clear` \u2014 instead of a plain true\/false value. It's used to handle error, ok, not-modified, and empty results from the catalog fetch.\n\n**Why**\n\nThis is an internal refinement to how Claude Code schedules retries after a failed or unusual model-catalog fetch, replacing a simple flag with more descriptive states.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}