> 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/~/changes/Sh4xqs4GDClkDKT9Hvux/references/database-information-and-organization/application-not-responding.md).

# Application not responding

Collector for macOS records *application not responding* events from devices in much the same way as Collector for Windows. Applications that do not respond to user input have a negative impact on the overall experience of employees and thus are an important part of the Digital Experience Score (DEX). Refer to [DEX score](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/dex-score.md) documentation for more information.

The technique employed by Collector to determine whether an application is not responding on macOS differs from the method used on Windows. This article describes how Collector measures an application not responding to events on each platform.

### Application not responding on Windows <a href="#applicationnotresponding-applicationnotrespondingonwindows" id="applicationnotresponding-applicationnotrespondingonwindows"></a>

On Windows, Collector regularly checks the responsiveness of applications by sending messages to their open windows. When an application does not process these messages timely, the system creates a new application not responding event.

### Application not responding on macOS <a href="#applicationnotresponding-applicationnotrespondingonmacos" id="applicationnotresponding-applicationnotrespondingonmacos"></a>

On macOS, Collector relies on the operating system logs to know whether an application is not responding. However, macOS reports unresponsiveness only after the user has forcefully quit an application.

For example, if an application is not responsive at some point, but eventually recovers, Collector does not report the application as not responding as long as the employee did not force the application to quit.


---

# 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/~/changes/Sh4xqs4GDClkDKT9Hvux/references/database-information-and-organization/application-not-responding.md?ask=<question>&goal=<user_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.