# Deviation

When you [enable a service](/1-9-0/documentation/services/setting-up-and-configuring-services/enabling-services.md), all its resources should transition from *disabled* to *enabled*, or to any other target state specified in the commissioning file. This file describes the resources and their required target states to ensure that the service functions properly.

However, certain conditions may prevent resources from achieving the desired target state (e.g. a broken network cable). Such instances are called a *deviation* and the affected service is considered *deviated*.

A pop up message notifies you of deviated services. To see the list of deviated services, click the arrow down button.

<figure><img src="/files/fmeRKMQPHfzYUDXMffzF" alt=""><figcaption></figcaption></figure>

It is also shown in the Services view, in the [Service Details view](/1-9-0/documentation/services/service-details-view.md), and in the list of the respective [resource](/1-9-0/documentation/resources.md). Clicking on the deviation warning messages will show a list of resources whose actual state is different from the expected state:

<figure><img src="/files/k1E5h6vWruiZuk1uFbNE" alt=""><figcaption></figcaption></figure>

To see which resources of a service are deviated, click a service name in the list. This opens the `Deviations` tab for the service to display the deviated resources. On the `Deviations` tab, you can see expected status and the actual status of each deviated resource.

<figure><img src="/files/3hTp7OjQ4mMcXzCIFBJf" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cybus.io/1-9-0/documentation/services/deviation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.