> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-7-2/documentation/services/deviation.md).
# Deviation
When the user chooses to [enable a service](/1-7-2/documentation/services/working-with-service-commissioning-files.md#enabling-services), all resources should change their state from *disabled* to *enabled*, or whatever other target state is specified in the commissioning file. In other words, the commissioning file specifies the set of resources and their expected target state which are needed to make the service work correctly.
However, in real-life there are always conditions that can not fully be controlled by the Connectware (such as a broken network cable), which can block one or more resources to reach the desired target state (e.g. having a healthy connection). This situation is called a *deviation*, and the corresponding service is said to be *deviated*.
The occurrence of such a deviation is indicated in the Admin-UI by a small yellow popup window message.
It is also shown in the [service overview page](/1-7-2/documentation/services/working-with-service-commissioning-files.md), in the [service details view](/1-7-2/documentation/services/service-details-view.md), and in the list of the respective [resource](/1-7-2/documentation/resources.md). Clicking on the deviation warning messages will show a list of resources whose actual state is different from the expected state:
This indication should express the difference (potentially caused by outside conditions) from the expected behavior of an enabled service.
---
# 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://docs.cybus.io/1-7-2/documentation/services/deviation.md?ask=&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.
