{"version":"2.1.235","anchor":"oauth-refresh-recognises-an-account-on-hold-response","canonical_anchor":"oauth-refresh-recognises-an-account-on-hold-response","heading":"OAuth refresh recognises an 'account on hold' response","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/oauth-refresh-recognises-an-account-on-hold-response","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### OAuth refresh recognises an 'account on hold' response\n\nOAuth token refresh now recognizes an 'account on hold' response as its own outcome\n\n**Unclear.** Whether the account-on-hold gate is enabled for any account has not been read yet.\n\nA refresh failure returning HTTP 400, 401 or 403 with a recognized hold payload is now classified separately from other failures. The refresh token is remembered in a hold map, a URL for the user is stored, and the refresh call returns a distinct outcome rather than being counted as a dead token or a generic failure. A new telemetry event fires on this path.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}