> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/pos-pairing/troubleshooting-pos-pairing/pos-was-unable-to-pair.md).

# POS was unable to Pair

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/S9M19Tvujb1vS7NEM8kf/images/image34.jpeg)

This message displays of one of the following reasons:

* The pairing failed. Repeat the steps in the Pairing after the initial Auto Upgrade, Pairing Expired or Revoked section.
* The Pairing Service was not started on the Commander via Configuration Client. Follow the steps in the Pairing after the initial Auto Upgrade, Pairing Expired or Revoked section.
* An incorrect Pairing Session OTP was entered. Select \[Pair POS] and Retrieve another Pairing OTP from Configuration Client in the Pairing after the initial Auto Upgrade, Pairing Expired or Revoked section.

{% hint style="info" %}
If the message "Unable to pair, please try again" displays, press \[Pair POS] again within a few minutes. Otherwise, the Pairing Service will need to be restarted.

If the "Unable to pair at this moment, please try again" message displays, it means that a different POS workstation is currently being paired with the Commander.
{% endhint %}


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/pos-pairing/troubleshooting-pos-pairing/pos-was-unable-to-pair.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.
