---
title: "Active vs Idle Session State in Insights Report"
slug: "active-vs-idle-session-state-in-insights-report"
updated: 2025-09-08T12:29:39Z
published: 2025-09-08T12:29:39Z
canonical: "support.controlup.com/active-vs-idle-session-state-in-insights-report"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Active vs Idle Session State in Insights Report

If you are using our Hybrid Cloud product, see the [VDI & DaaS reports](https://support.controlup.com/docs/historical-reports) category for details on this report.

ControlUp classifies Insights user sessions as Active or Idle. The session state is displayed, both in Insights and in the console.

### Overview

When viewing user session reports in Insights, the user session state is displayed as Active or Idle. The Idle/Active status of a session is based on the time elapsed since the last user input was received in the user session.

By default, sessions are set to timeout and become idle after 30 minutes. For example: If a session is in Active State AND the Idle Time is lower than 30 minutes, the session is considered active. If a session is in Active State AND the Idle Time is higher than 30 minutes, the session is considered idle.

This can be modified to suit your needs as described in the section below.

In the examples below, the default setting of 30 minutes is in use.

The following is an example of how the user session state appears in Insights:

![user session details report](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/1%20(1).PNG)

The following is an example of how the user session state and idle time are displayed in the console:

1. Active in Insights
2. Idle in Insights

![sessions view in console](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/2%20(1).PNG)

### Timeout Configuration

The idle timeout can be modified per machine via the machine's registry editor.

**To modify the idle time timeout:**

1. Open *regedit.exe* on the machine with the ControlUp Agent installed.
2. From the computer's registry, locate and select the following registry entry:  
**`HKEY_LOCAL_MACHINE\Software\Smart-X\ControlUp\Agent\IdleTime`**
3. If the **IdleTime** value does not appear in the Registry, you need to create it by right-clicking **Agent** > **New** > **DWORD**, and a new value appears in the Registry.  
Right-click on the new value and click **Rename** and rename the value **IdleTime**.  
![HKEY_LOCAL_MACHINE\Software\Smart-X\ControlUp\Agent\IdleTime key with new value](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/mceclip6.png)
4. Click the **IdleTime** value and the Edit DWORD Value popup appears.  
![Edit DWORD Value popup](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/mceclip1%20(4).png)
5. Under **Value data,** enter the amount of time, in minutes, you want idle sessions to timeout and set the **Base** to **Decimal.**
6. Once you've entered the requested values click **OK**, and the new value appears in the data column.
7. Restart the ControlUp Agent Windows service, and the newly set idle timeout is implemented.