> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/vdi-experience/using-sessions-overview/sessions-2.md). # Executions tab See a list of all binary executions on VMs in all active sessions.

Select a device name in the **Device > Name** column to access [**Device view**](/user-guide/device-view.md) for the specific VM. ### Action menu Use the contextual action menu to refine your troubleshooting by allowing different data exploration paths.

In the **Username**, **Device > Name** and **Binary > Name** columns, select the action menu on the right side of the selected binary to open a new contextual investigation to **Retrieve all** connected devices, users, or events. In the **Binary > Name** and **Device > Name** columns, you can **Diagnose** execution crashes or high CPU usage. In the following columns, select **Drill down to** in the action menu to open a new contextual investigation to further diagnose issues and remediate them using remote actions: * Username * CPU time * Memory used * Page faults * Number of freezes * File total bytes * File total operations * Network total traffic --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nexthink.com/user-guide/vdi-experience/using-sessions-overview/sessions-2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.