> 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/2-6-1/data-flows/services/managing/disabling.md).
# Disabling Services
Disable individual or multiple services in Connectware to stop their containers, connections, endpoints, and mappings.
You can disable services in their corresponding **Service Details** view or disable multiple services at once in the **Services** view.
{% hint style="warning" %}
Disabling a service will terminate all running containers, active connections, endpoints, and mappings associated with it. However, volumes will remain unchanged and will automatically reattach to the service when it is re-enabled.
{% endhint %}
## Disabling Multiple Services
1. In the navigation panel, click **Services**.
2. In the **Services** view, activate the checkboxes of the services that you want to disable.
3. Click **Disable**.
4. In the **Disable Services** dialog, click **Disable**.
## Disabling a Service from its Service Details View
1. In the **Service Details** view of a service, click **Disable**.
2. In the **Disable Service** dialog, click **Disable**.
3. In the **Disable Services** dialog, click **Disable**.
---
# 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/2-6-1/data-flows/services/managing/disabling.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.
