Skip to content

Back off from successive requests when sync results in a 401 #88317

@Tyriar

Description

@Tyriar

Currently it appears that when settings sync gets a 401 unauthorized it will continue to sync (and fail) on the standard interval. We should instead stop syncing immediately and show a warning that there is a problem with auth. If the server gives a 401 that means it's available and function and the token failed verification, it is guaranteed to continue to fail verification if the same token is used.

Related #85211 (this is more appropriate for 50x and 404s)

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions