TCP In node does not like environment variables

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.

Please open an issue.


Thank you

1 Like

Issue fixed and confirmed working in version 3.1.6


This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.