You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Desktop (please complete the following information):
OS: linux
Browser: chrome
Version
Additional context
The basic problem here is that the homeserver is returning 500s, because it's so busy sending out device list updates after the /login. So in many ways the root cause is matrix-org/synapse#7721.
However, Hydrogen could usefully keep retrying, or give the user a "try again" option, rather than the only option being to log out and start again.
Hmm, it's somewhat annoying that the server returns a 500 rather than a 429 if the client should retry, but can't immediately think of any downsides of also retrying (for all requests, not just /keys/upload) on 500... at least a few times otherwise you'd never find out about a potential genuine server error.
500 generally means "server failed to process this request". I'd say it's expected behaviour for any REST client to retry on a 500. More so than a 429.
Activity
llwp commentedon Mar 4, 2022
Definitely a good ~feature suggestion imho.
bwindels commentedon Mar 9, 2022
Hmm, it's somewhat annoying that the server returns a 500 rather than a 429 if the client should retry, but can't immediately think of any downsides of also retrying (for all requests, not just /keys/upload) on 500... at least a few times otherwise you'd never find out about a potential genuine server error.
richvdh commentedon Mar 9, 2022
500 generally means "server failed to process this request". I'd say it's expected behaviour for any REST client to retry on a 500. More so than a 429.