> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/troubleshooting/edit-watch.md).

# Edit watch

## Overview

Unexpected symptoms which may be seen when editing a watch.

## Symptom 1. Interface greyed out on Main tab

If a watch is displaying a greyed out non-editable interface on the Main tab, this is due to `"Applications(AppVis)"` being selected for autodiscovery in the Features tab.

To change the interface if required, click technical test and select from the list.

{% hint style="info" %}
Changing the interface may stop AppVis gathering traffic statistics if the device configuration does not match the new Highlight selection.
{% endhint %}

## Symptom 2. Bandwidths greyed out on Main tab

If a watch is displaying greyed out non-editable bandwidths on the Main tab, this is due to Bandwidth being selected for autodiscovery in the Features tab.

To view or change the originally configured bandwidths, uncheck bandwidth autodiscovery on the Features tab then view the Main tab for the bandwidth values.

To change the bandwidths configured but leave autodiscovery, save the bandwidth changes first then re-edit and add back bandwidth autodiscovery.

## Symptom 3. Broadband Clarity will not enable

If the Broadband Clarity feature will not enable when in Edit watch, check that the watch type was originally activated in Highlight as an ADSL service. If not, and was incorrectly set as symmetric (type `"bearer"`), then the only way to enable Broadband Clarity is to first re-add the watch as ADSL or Broadband.


---

# 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://help.highlight.net/troubleshooting/edit-watch.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.
