> 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/classes-of-service.md).

# Classes of Service

## Overview

This page explains symptoms experienced with discovering Classes.

## Symptom 1. No classes discovered

When viewing the Location watch status panel having clicked on a heat tile, if no classes are seen then the likely causes of this are:

* There is no outbound QoS policy defined and applied to the monitored interface. Classes are not discovered if only an inbound policy is applied.
* There is no child QoS policy with class names configured under a shaper policy applied to the monitored interface.
* The outbound QoS policy has been applied to an interface not being monitored by Highlight.
* Highlight has not been configured to autodiscover classes.
* The class names used do not match **\[those set up in Highlight using the CCD]** (→ <https://support.highlight.net/help/admin/ccd>)
* Highlight CCD changes not yet adopted by poller/watch. It will take up to 4 hours for Highlight pollers to adopt the new CCD. A watch will need to revalidate for any new classes to be discovered which generally happens following device reconfiguration or otherwise every 32 days.

## Symptom 2. Only Best Effort class discovered

When viewing the Location watch status panel having clicked on a heat tile, if only Best Effort class is seen then possible causes of this are:

* An outbound policy has been applied with no classes defined, for example a shape policy.
* The class names used in the outbound policy do not correspond to the standard service provider class names defined in Highlight.


---

# 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/classes-of-service.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.
