# Fail Action

The **Fail Action** node intentionally fails a stream. It can be used to stop processing immediately when a specific condition is met, or to mark a workflow as failed on purpose.

In **FX triggers**, failing a stream also affects the trigger chain: any subsequent streams assigned to the same FX trigger will be skipped.\
Example: If an FX trigger has four streams and the second stream ends with a Fail Action, streams three and four will not run.

{% hint style="warning" %}

#### Use Case Scope

This node is applicable only to **FX streams**.

For **IO, CO, and HK** workflows, use the **Job Status Update Action** as the equivalent mechanism to influence job/state handling.
{% endhint %}

#### Input Parameters

**Message (optional)**\
Optional error message returned with the failure. This can be used to document why the stream was intentionally stopped.

<figure><img src="/files/hfyWjwK62ZsYHhIj4c6q" alt="" width="350"><figcaption><p>Fail Action</p></figcaption></figure>

#### Behavior

* Always fails when executed
* Immediately marks the stream as failed
* In FX triggers, prevents any subsequent streams in that trigger chain from running
* Allows connecting additional nodes after it, but only the **fail output** can be used

#### Typical Use Cases

* enforcing validation rules (e.g., required metadata missing)
* hard-stopping an FX workflow when a prerequisite is not met
* preventing follow-up streams from running if a critical condition occurs
* returning a clear error message to operators or logs

#### Important Note

Use this node only when failing is the desired outcome.\
If the goal is to continue the workflow but handle an error gracefully, use conditional logic or a Success Action (for non-critical failures) instead.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/misc-21/fail-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.