Inactivity timeout

[KatePalmerLilley]

I'd like to know more about inactivity timeout, such as:

• how long it it supposed to be?
• I've noticed that if it timeouts in the middle of creating or amending the an item, the changes aren't saved - is it possible to have a timeout warning?
• the orchestra never seems to timeout.

[pjmonks]

When you are logged in, if you did nothing else in the Mauro UI or Orchestrator (e.g. didn't click any buttons to perform an action), then you would be automatically logged out after 30 minutes. This does work in the Orchestrator too - I've seen it happen. It is referred to as a "rolling" timeout though, meaning as long as you performed an action in Mauro (including fetching data), that keeps your login session "alive" and active, which will count 30 minutes from your last action.

Any requests to change that or add new features around that, such as your suggested warning, needs to be raised to @jamesrwelch and the Mauro team, that is outside the scope of System C's work.

[AngelaFaulding]

@jamesrwelch - as per Peter's message above, can you look at a warning message please?