Workflow Studio session timeout not resetting when saving work

[Ron28]

I wonder if anyone else has noticed, when spending  a lot of time in Workflow Studio I have noticed that the default 30 minute inactivity timeout is not reset when clicking on 'save'. Nor is there an "extend session" warning so it has logged me out after 30 minutes regardless.

I usually have a few browser tabs open to tables etc, but at the time was only updating the browser session that has Workflow Studio open. I can understand that most of the work there is done on the client side, but when you save your session I would have expected the server to realise you are still active.

Yesterday I took down some times:
4:30pm - logged in again after having been kicked out of Workflow Studio
4:38pm - Saved my changes
4:41pm - Saved my changes
4:44pm - Saved my changes
4:55pm - Saved my changes
5:00pm - Logged out of Workflow Studio with a message "logged out due to inactivity for 15 minutes"
From the timings, the 30 minutes matches the glide.ui_session_timeout. But having saved it multiple times within that 30 minutes, the system does not reset the inactivity timer. And there is no warning, which does appear in one of the other open browser tabs to the instance. All tabs log out at the same time.

I guess this is a bug?

Ron

[Mark Manders]

To users this seems to be a bug, but you can create a case with NowSupport and they will tell you that this works as designed. You really need to make calls to the server to stay active in the system and apparently Workflow Studio is not one of those things that does that.

But, since you are talking about working in there, you are probably not on a production instance, so why not extend the logout timer there and include it in the clone preservers, so you don't have to reset this after each clone? 

[Ron28]

Strange though as when you save the flow it you can see that in the system logs so I would have thought that would reset the ITO. But doesn't, so I still think it is a bug.
I understand that all actions in Flow Designer are done on the client side. Just saving the flow is, if the system logs are to be believed, a call to the server.