@christianroth this is not intended behaviour at all. Have you seen this behaviour repeatedly? In particular, have you seen this happening shortly after logging in to MWO as well?

I ask the latter question because the session idle period is 2 hours, so if the device was idle for more than that period, and then you went into MWO and tried an action, you’d get prompted to re-authenticate when the action you did gets synced when in reality they are in fact independent events. 

Could you also share the Device Logs with me please so that we can see if the logs reveal anything - I’ll send you a direct message with my e-mail address. In case you’ve not done this before, the Device Logs are accessible by going into the Settings menu, and then Send Device Logs > Share.

Thanks,

Rukmal

@Rukmal Fernando We (I work with Christian) have created a case for this: CS0291268. There you will find devicelogs.

This is fully replicable and you’re instantly logged out when the issue occur. For eg open a worktask that has an attachment that the user doesn’t have access to → instant logout. Ie no correlation to how long you have been logged in before the issue occur.

We also see that the logout mechanics in this instance seem create an issue where multiple users have been faced with 400 bad gateway when trying to login again.

Kr,

/Magnus