> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/command-line-interface/reference/workbench/workflows-versions-delete.md).

# workflows versions delete

Delete a version of a workflow from a namespace

## Synopsis

```shell
omics workbench workflows versions delete VERSION_ID 
  [--workflow=WORKFLOW_ID]
  [--force]
```

## Description

Delete a specific version within a workflow. When a version is deleted, it becomes unusable for future runs, but a reference to the version is retained for provenance purposes.

## Examples

Delete a version

```shell
omics workbench workflows versions delete v1 --workflow wf12345
```

Delete a version using the `--force` flag without prompting for confirmation:

```shell
omics workbench workflows versions delete v2 --workflow wf67890 --force
```

## Positional Arguments

### `VERSION_ID`

**Required**. Specify the identifier of the version that you want to delete.

## Flags

### `--workflow`=`WORKFLOW_ID`

**Required**. Specify the identifier of the workflow from which you want to delete the version.

### `--force`

Delete the version without prompting for confirmation. Use this flag if you want to force the deletion.


---

# 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.omics.ai/products/command-line-interface/reference/workbench/workflows-versions-delete.md?ask=<question>&goal=<user_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.