> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent-ios-guide/8.8/device-user-tasks/view-device-and-app-status-and-information/view-connection.md).

# View Connection

View general and connection information for your Cortex XDR agent app for iOS.

View general information and the connection between the iOS device and Cortex XDR or Cortex XSIAM.

1. From the Cortex XDR home screen, select Settings → **Managing Server**.

   The screen indicates the iOS device server connection, along with the Cortex XDR or Cortex XSIAM **Server Address** and **Last Connection Time**. It shows the last time a check in was performed successfully.
2. Test a forced heartbeat with the server by tapping **Check In Now**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-agent-ios-guide/8.8/device-user-tasks/view-device-and-app-status-and-information/view-connection.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.
