{"version":"2.1.269","anchor":"401-recovery-function-gains-a-completion-callback","canonical_anchor":"401-recovery-function-gains-a-completion-callback","heading":"401-recovery function gains a completion callback","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/401-recovery-function-gains-a-completion-callback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### 401-recovery function gains a completion callback\n\nThe internal 401 (unauthorized) recovery routine can now report its result back to the caller\n\n**What**\n\nThe internal routine that tries to recover when a request fails with a 401 (unauthorized) error can now take an optional callback function that is told the actual outcome of the refresh attempt, instead of only returning a simple true\/false. This is intended for callers such as SDK-style, non-interactive consumers that need to know the specific result rather than just whether recovery succeeded.\n\n**Why**\n\nThis lets programmatic integrations react more precisely to authentication failures instead of only learning that something went wrong.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}