# CLIENT161: This tab does not run the register

## What this means[​](#what-this-means "Enlace directo a What this means")

This tab does not currently run the register, so it did not send a new payment request.

On the web, only one browser tab runs the register at a time. If a second tab is opened, or another tab takes over, this tab stops running the register and shows a screen saying so. A payment request that was about to start when that happened was refused before it was sent, and this entry records the refusal. It is informational: nothing failed on your store or your device, and it does not describe the outcome of any payment that had already started.

## Your data[​](#your-data "Enlace directo a Your data")

The refusal wrote and lost nothing. Sales, carts and orders already saved on this device are unaffected and sync as normal. A payment that had already started — a card on the reader, or a capture already sent to the store — was not interrupted by this entry. Its outcome is recorded on the order once the tab that now runs the register has synced it, so check that order before taking the payment again.

## Troubleshoot[​](#troubleshoot "Enlace directo a Troubleshoot")

1. Look at the register screen in this tab. It tells you whether another tab is running the register; choose **Take over here** to continue in this tab, or carry on in the other tab.
2. If the screen offers **Reload**, reload the tab. The register comes back in this tab once it has reloaded.
3. Before retrying a payment that had already started, open the order and check its payment status, so a payment the customer has already made is not taken twice.

## Details[​](#details "Enlace directo a Details")

* Código

  `CLIENT161` (`REGISTER_TAB_NOT_OWNED`)

* Gravedad

  info

* Introducido en

  WCPOS

  <!-- -->

  2.0.0