We're always looking for ways to help our customers spend their investments cost-effectively. During the past few months, we have been rolling out changes that allow us to better monitor learner (in)activity and terminate track environments after a (configurable) idle timeout. We've gotten great responses from those who have tried it so far, and the feature is now generally available. 

The new Idle timeout feature will trigger a warning message to learners who sit idle through a session without interacting with your content. If they don't confirm they're still there within 2 minutes, the environment will be terminated automatically.

The idle timeout is configurable per track. For example, let's say that you've set the idle timeout on your track to 300 seconds (5 minutes). If the user has been idle for 3 minutes, a warning message will pop up and ask the learner to respond. If after 2 minutes there's no response, the environment will be terminated. So the user will always have two minutes to react. 

In the case of live events, it may not be desirable to have tracks time out after a short idle time (for example while you’re presenting at a workshop). In those cases, we recommend not setting an idle_timeout value, or duplicating the track without an idle_timeout value.

To learn more about the idle timeout functionality and how to configure it, check out this Instruqt Docs and search for Idle timeout.