> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-nodes/pipeline-control-node.md).
# Pipeline control node
## Overview
The *Pipeline Control* node allows you to control the pipeline execution state at any point. You can force a fail state, a stop, write specific log output, or add warnings. This node can be especially useful when testing a pipeline for different outcomes.
## Available pipeline control methods
Having added a *Pipeline Control* node, click it once to access available options:
From here, select the required `method` and configure settings. The following methods are available:
Fail
Marks the run as failed and triggers any configured [error handling options](/documentation/brigge-for-transformers/pipelines/pipeline-settings.md#pipeline-error-handling):
{% hint style="info" %}
Log messages can include static text and [variables](/documentation/brigge-for-transformers/pipelines/pipeline-variables.md).
{% endhint %}
The pipeline run fails at the point this node is placed and the failure is recorded in [logs](/documentation/brigge-for-operators/history-and-retries.md). For example:
{% hint style="info" %}
You might use this option when an important condition must be met, otherwise the run should be treated as an error.
{% endhint %}
Stop
Stops the run cleanly (without marking it as a failure) at the point this node is placed:
Run [logs](/documentation/brigge-for-operators/history-and-retries.md) show that the run stopped. For example:
{% hint style="info" %}
You might use this option if you are testing part of a pipeline and don't need it to run to completion.
{% endhint %}
Write log
Records the specified log message and severity level to the run log, without affecting execution:
{% hint style="info" %}
Log messages can include static text and [variables](/documentation/brigge-for-transformers/pipelines/pipeline-variables.md).
{% endhint %}
You can set the log message severity to `success`, `warning`, `danger`, or `info`. This message is then written to logs. For example:
{% hint style="info" %}
This option is particularly useful when something must be recorded for debugging or auditing purposes.
{% endhint %}
Add warning
Flags a warning with the specified log message, without stopping the run:
{% hint style="info" %}
Log messages can include static text and [variables](/documentation/brigge-for-transformers/pipelines/pipeline-variables.md).
{% endhint %}
This message is then written to logs. For example:
{% hint style="info" %}
This option is particularly useful when something is notable but not serious enough to fail or stop the run.
{% endhint %}
