[sususu]

In the web at least it was returning 500, I guess that the desktop/mobile apps make some check in intervals. When the backend returned 500 the app thought that the current login could not be authenticated and logged out everybody

[benatkin]

I think some will aggressively log out even on 500s. If you log out 500s that's not the same as logging out failed network requests. The server has to actually send a response, so while it will erroneously log out sometimes, in a reliable api, or one that sends errors in 200s but is otherwise reliable, it won't be so often that a whole lot of users give up. Plus some API middlewares will default to hiding error response codes for security and always send 500 no matter what the upstream response code (this assumes the error codes aren't needed by the devs because they can look at the logs).

I've seen logging out on failed network requests, but that is highly annoying and frequently occurs and typically just a coding mistake.