> 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/deleting.md).
# Deleting Services
Disable and delete services that you no longer need in the Services view of Connectware.
{% hint style="warning" %}
When a service is disabled, all running containers, active connections, endpoints, and mappings are stopped. Volumes are not affected and will automatically reattach when the service is re-enabled.
{% endhint %}
1. Before deleting a running service, you must disable it first. For details, see [Disabling Services](/2-6-1/data-flows/services/managing/disabling.md).
2. In the navigation panel, click **Services**.
3. In the **Services** view, activate the checkboxes of the services that you want to delete.
4. Click **Delete**.
5. In the **Delete Service** dialog, click **Delete** to delete the service.
{% hint style="info" %}
After deleting a service, there is a waiting period required before you can install another service with the same service ID. You can customize the waiting period via the `CYBUS_SERVICE_REINSTALL_DELAY_SECONDS` [environment variable](/2-6-1/reference/environment-variables.md).
{% endhint %}
---
# 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/deleting.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.
