{"version":"2.1.267","anchor":"policy-limits-fetch-now-uses-an-abortcontroller-and-reports","canonical_anchor":"policy-limits-fetch-now-uses-an-abortcontroller-and-reports","heading":"Policy-limits fetch now uses an AbortController and reports cycle_aborted","tier":"internal","area":"Policy Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/policy-limits-fetch-now-uses-an-abortcontroller-and-reports","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Policy-limits fetch now uses an AbortController and reports cycle_aborted\n\nPolicy-limits fetches can now be cleanly aborted, logged as 'cycle_aborted'\n\n**What**\n\nThe component that fetches policy limits now uses an `AbortController` to cancel in-flight network requests. Its abort signal is passed into the fetch call and gets recreated whenever the fetcher is stopped. If a fetch is aborted, or if the session generation changes mid-flight, the outcome is now logged as `cycle_aborted`, and the `fetchAndLoad` function checks for this aborted state in addition to its previous check for a changed session generation.\n\n**Why**\n\nThis makes policy-limits fetching more robust by properly canceling requests that are no longer needed and giving clearer diagnostic information when a fetch is interrupted, rather than letting stale or interrupted requests run to completion silently.\n\n- Area: Policy Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}