Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AuthArea: what it touches
In DevelopmentKind: in v2.1.235,
In DevelopmentSection of the release
Unclear Whether the account-on-hold gate is enabled for any account has not been read yet.
A 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the account-on-hold gate is enabled for any account has not been read yet.
