> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/verifone-hq/device-management/editing-devices/sub-status-for-inactive-devices.md).

# Sub status for inactive devices

This section discusses sub status for in active devices.

<details>

<summary>Keywords</summary>

Also called: inactive sub status. Search terms: device swapped, device missing, tablet communication issue, system defined, user defined.

</details>

## What is a sub status?

Inactive devices can be assigned a **Sub Status**. This feature allows more precise categorizing of devices beyond *Inactive*, identifying the reason a device entered that status.

## When VHQ assigns a sub status automatically

There are specific cases where the system automatically marks a device inactive and assigns a sub status:

* When a device is swapped, the swapped device's status is marked inactive with a sub status of *Device Swapped*.
* When a device fails to contact the server for a specific time period, its status is marked inactive with a sub status of *Device Missing*.
* When a tablet (which communicates with the VHQ server through the MDM server) fails to contact the VHQ server, its status is marked inactive with a sub status of *Tablet Communication Issue*.

## Sub status types

* **System defined**: Integrated into the system. Cannot be assigned, edited, or deleted by the user.
* **User defined**: Created by you, and can be edited or deleted by you.

## Guidelines

* You can assign a sub status from the *Device Search* and *Device Profile* screens.
* Once created, a sub status can be assigned to *Inactive* devices from *Device Search*, *Device Profile*, *Importing .xml file*, or *Timed Import*.
* You can select multiple devices in *Device Search* and assign a sub status to all of them at once.

## Related topics

* [Device status](/support-us/verifone-hq/device-management/editing-devices/device-status.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.verifone.com/support-us/verifone-hq/device-management/editing-devices/sub-status-for-inactive-devices.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.