1. What version of Thingworx are you currently running? 9.2
2. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Thingworx allows an idle time to be set after which the user is logged out. Unfortunately any service call from a mashup resets this timer, even in cases where the service is being called due to an auto-refresh of data.
I appreciate there are numerous scenarios (e.g. dashboards on TVs) where the current approach is preferable. I would suggest a setting on the mashup design, or on the service itself, to indicate whether the service calls should count as user activity or not.
3. What business value would your suggestion represent for your organization? Improved security of the platform, and an actual idle timeout that works. Currently if a mashup had any kind of auto-refresh, the user would never be logged out.