> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/pipelines/deleting-a-pipeline.md).
# Deleting a Pipeline
Only the Partek Flow user that created or imported a pipeline and administrative users have the ability to delete a pipeline. The delete option is not available to non-administrative users that that did not create or import a particular pipeline. To delete a pipeline:
1. Click on a circular [data node](/partek/partek-flow/tutorials/creating-and-analyzing-a-project/the-analyses-tab.md#data-and-task-nodes) under the [*Analyses*](/partek/partek-flow/tutorials/creating-and-analyzing-a-project/the-analyses-tab.md) tab and expand the **Pipelines** section from the menu on the right. The [context-sensitive menu](/partek/partek-flow/tutorials/creating-and-analyzing-a-project/the-analyses-tab.md#the-context-sensitive-menu) will only display pipelines that can be applied to the data type of the selected data node
2. Click **Delete pipeline** () for the pipeline you want to delete (Figure 1)\\
Figure 1. Delete a pipeline. The red cross icon will not be available to non administrative users that did not create or import a particular pipeline
3. You will be asked if you are sure you want to delete the pipeline (Figure 2). Click **Delete**.
Figure 2. Confirm pipeline deletion
## Additional Assistance
If you need additional assistance, please visit [our support page](https://www.illumina.com/company/contact-us.html#/other/technical-support) to submit a help ticket or find phone numbers for regional support.
---
# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/pipelines/deleting-a-pipeline.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.
