TCP In node does not like environment variables

[maximus]

When writing a variable name on the TCP In node port, it works as expected but the node shows the little red triangle and a warning is displayed when deploying the flow.
Is this expected behaviour or can I open an issue in Github?

For information, the TCP Out node behaves graciously when adding an environment variable.

[Steve-Mcl]

@maximus

Is this expected behaviour or can I open an issue in Github?

Please open an issue.

[maximus]

@maximus

When writing a variable name on the TCP In node port, it works as expected but the node shows the little red triangle and a warning is displayed when deploying the flow.

Done,

TCP In node gives warning with environment variables

Thank you

[dceejay]

Issue fixed and confirmed working in version 3.1.6