> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting.md).
# Workflow: Hard reset troubleshooting
## Overview
Organizations often deal with unexpected hard-resets on endpoints. IT teams usually learn about these issues through tickets, leading to manual investigations. Our workflow streamlines this by surveying employees, collecting technical data, and applying remediation steps, saving time and improving efficiency.
## Problem
When you detect a hard reset, you do not actually know the reason. Indeed, employees in your organization often trigger forced shutdowns, but you don't know when or why. You only take remediative action when tickets are raised, and even then, it requires manual investigation and reaching out to the end user to understand why an employee decided to force a device shutdown and ultimately perform a proper root cause analysis and remediation.
## Solution
When you detect a hard reset, you do not actually know the reason. Indeed, employees in your organization often trigger forced shutdowns, but you don't know when or why. You only take remediative action when tickets are raised, and even then, it requires manual investigation and reaching out to the end user to understand why an employee decided to force a device shutdown and ultimately perform a proper root cause analysis and remediation.
## **Expected value**
This fully hands-off hard reset troubleshooting workflow will:
* Detect hardware resets before tickets are raised.
* Reduce time spent on manual investigations.
* Find out the reasons behind hard resets.
* Automatically apply fixes for common causes of hard resets.
## Get started
Configure and start using your packs by following these links:
* [Usage guide: Hard reset troubleshooting](/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting/usage-guide_-hard-reset-troubleshooting.md)
* [Configuration guide: Hard reset troubleshooting](/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting/configuration-guide_-hard-reset-troubleshooting.md)
---
# 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/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting.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.