> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/setup-docs/troubleshooting/request-player-status.md).

# Request Player Status

Player status information is likely to be requested by our support team when investigating issues.

There are two ways to request the status, which is dependent on whether your Displays are showing as connected are not:

{% tabs %}
{% tab title="Connected and Logged in" %}

1. Click on **Displays** from the main CMS menu
2. Use the row menu for the Display and click **Request Screenshot**
3. Use the **Columns** drop down and ensure that **Screenshot** is ticked
4. Click the thumbnail shown in the grid
5. Click on the `i` icon in the top right corner of the thumbnail
6. Scroll down to **Player Status**
7. Capture the status to attach to your support ticket
   {% endtab %}

{% tab title="Not Connected" %}

1. Connect a mouse to your device
2. Click on the screen whilst Xibo is running
   1. For webOS click the yellow button whilst Xibo is running
   2. for Tizen click OK on the remote whilst Xibo is running
3. Click **Status** from the Action bar at the top of the screen
4. Capture the status to attach to your ticket
   {% endtab %}
   {% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/setup-docs/troubleshooting/request-player-status.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 `build a script that syncs our docs to a CMS` 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.