I would suggest you put the OnTimer script in the hosted file instead of the local file. Have it do something harmless, like set the value of a global field, each time it fires.
The logout from the server is looking for idle time. By performing an action in the hosted file from the client, you reset the idle timer and prevent it from being shut down.
Just out of curiosity, what is the driver for keeping a file open continuously? There are certain risks associated with doing that; might be a better way to achieve the objective.
Thank you Mike, for your input.
I actually do have an OnTime script on the hosted file (I can't tell if it always runs, but it should). It still disconnects, but maybe it's not doing something active enough? (It's updating a webviewer.)
I'm keeping it open because it's showing a status of something that people need to quickly see walking by, which the status can be changed elsewhere.
Updating a Web Viewer (Refresh Object?) might not do it. I'm not 100% sure exactly what causes the idle timer to reset. I think there was a post here a little while ago; try searching for "idle" and see what comes up. But I think something more like a user action is needed - a key press, mouse movement, etc. So an Insert step might keep it from timing out.
But that's the angle I would pursue. Figure out what resets the timer and leverage that.
Ok, I will test things out, thanks