> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/pipeline/configuring-pipeline-steps/editing-a-pipeline-step.md).
# Editing a Pipeline Step
{% hint style="warning" %}
#### Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article.
{% endhint %}
##  Overview
You can edit any field in a pipeline step, including **Name** and **Operation**. Editing a step lets you make minor or major changes to your pipeline without rebuilding it. This article gives you general instructions for editing a step. For instructions on editing the fields for a specific operation, see the article for that operation.
* [Pipeline Operation: Validate](/devops/pipeline/pipeline-operations/pipeline-operation-validate.md)
* [Pipeline Operation: Code Scan](/devops/pipeline/pipeline-operations/pipeline-operation-code-scan.md)
## Edit Validate Step
{% stepper %}
{% step %}
### Edit a Step
1. Click the step to edit.
2. Click **Edit**.
{% endstep %}
{% step %}
### Change Values
Every field of a step can be edited, including the **Name** and **Operation**. For details on changing each field, see the article on the corresponding operation you are editing.
* [Pipeline Operation: Validate](/devops/pipeline/pipeline-operations/pipeline-operation-validate.md)
* [Pipeline Operation: Code Scan](/devops/pipeline/pipeline-operations/pipeline-operation-code-scan.md)
1. Change any of the step's fields.
If you are changing the **Next Step** section, see the following warning and review the [Adding a Pipeline Step](/devops/pipeline/configuring-pipeline-steps/adding-a-pipeline-step.md) article.
{% hint style="warning" %}
#### Step Removal Warning
If a step has no paths to it, it will be automatically removed from the pipeline. This can occur, for example, if you insert a **Validate** step before a **Deploy** step and set both **On pass** and **On fail** to **Stop**. In this scenario, there is no longer a path to reach the **Deploy** step, and the pipeline automatically removes orphaned steps. See the diagram below to help visualize the issue.
{% endhint %}
{% endstep %}
{% step %}
### Save Changes
1. Click **Save**.
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/devops/pipeline/configuring-pipeline-steps/editing-a-pipeline-step.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.
