> 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-3/documentation/services/deviation.md).
# Deviation
When you [enable a service](/1-7-3/documentation/services/working-with-service-commissioning-files.md#enabling-services), 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.
It is also shown in the [service overview page](/1-7-3/documentation/services/working-with-service-commissioning-files.md), in the [service details view](/1-7-3/documentation/services/service-details-view.md), and in the list of the respective [resource](/1-7-3/documentation/resources.md). Clicking on the deviation warning messages will show a list of resources whose actual state is different from the expected state:
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.
---
# 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-3/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.
