# Deprecation warning

## Overview

Due to the constant development of Helmut4, it is possible that nodes may become deprecated once the system has been upgraded to a [newer snapshot release](/helmut4-releases/v4.9.1/getting-started/upgrade-guide.md). 

Related information about why a node has been deprecated or replaced with a newer one can be checked in the [changelog](/helmut4-releases/v4.9.1/release-notes/changelog.md).

## Finding a deprecated node

There are two indicators to find a deprecated node.

The first indicator can be observed within the [Streams](/helmut4-releases/v4.9.1/helmut4-components/helmutfx/streams.md) tab. Any stream containing deprecated node(s) will display a red triangle with an exclamation mark, accompanied by the hover information 'Contains deprecated nodes'.

<figure><img src="/files/FH2SmnwzlD3ojpsO97ZA" alt=""><figcaption><p>Deprecation warning in streams</p></figcaption></figure>

The second indicator can be found within the stream. Any deprecated node will feature a red dotted border for visual indication.

<figure><img src="/files/I2ZLgU28CJgavp8PrsqC" alt="" width="362"><figcaption><p>Deprecated node</p></figcaption></figure>

## Replacing a deprecated node

### Prologue

A deprecated node won't stop working after the system has been updated. By default, they continue operating as designed, but they won't be able to address any of the new features/functions added to the newer equivalent of this node.&#x20;

{% hint style="info" %}
We advise updating Helmut4 to a newer version and considering updating the nodes after a few days to ensure everything is working as designed, thereby reducing the amount of debugging in case of an issue.
{% endhint %}

### Replace deprecated node

Replacing a deprecated node is a manual task. This is because an automatic replacing mechanism would complicate debugging significantly, as there is no direct reference to where changes have been applied in the background.&#x20;

Automatic node replacement could also lead to issues with existing workflows and/or third-party applications, so consider testing in advance on your staging system.

Nodes can be replaced one-to-one. Please be cautious to avoid any copy/paste issues that may cause a syntax error.

### New parameters / options

{% hint style="warning" %}
Please allocate some time for this task, as it may be necessary to conduct pre-testing.
{% endhint %}

The functionality has been expanded, as illustrated in the screenshot below for the [EFS Add Groups to Media Space](/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/nodes/actions/third-party/editshare/editshare-file-system/efs-add-group-to-media-space-action.md) action, which now includes a Site UUID field.

<figure><img src="/files/UDZNZcTZkK4SW2Y399Yu" alt="" width="371"><figcaption><p>Deprecated and new version of an EFS node action</p></figcaption></figure>

<figure><img src="/files/WdR41OxDfaED3TxoR5gj" alt=""><figcaption><p>Deprecated and new version of a project file index action</p></figcaption></figure>


---

# 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/v4.9.1/helmut4-components/streamdesigner/deprecation-warning.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.