> 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-uk/ux700/how-tos/how-to-request-a-heartbeat.md).

# How to Request a Heartbeat

Request a heartbeat on a UX700 terminal to trigger any pending scheduled updates.

{% hint style="info" %}
**Use this when** you need to trigger any pending scheduled updates on a UX700 terminal by requesting a heartbeat.
{% endhint %}

Requesting a heartbeat prompts the terminal to check in and trigger any scheduled updates that are still pending. How you do it depends on your terminal's software version.

{% tabs %}
{% tab title="Below version .40" %}

1. Scroll down and select the **Launcher** (the 9-grid box icon).
2. Select **Diagnostic**.
3. Select **System**.
4. Select **Request Heartbeat**.
   {% endtab %}

{% tab title="Version .40 and above" %}

1. Tap the **three lines** to open the menu.
2. Select **Check for Updates**.
   {% endtab %}
   {% endtabs %}

<details>

<summary>Keywords</summary>

Also called: request a heartbeat, heartbeat, trigger update, force update, check for updates, pending updates. Search terms: heartbeat, request heartbeat, check for updates, pending update, scheduled update, diagnostic, system.

</details>


---

# 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-uk/ux700/how-tos/how-to-request-a-heartbeat.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.
