Streaming Engine
Workflows - the easy way
Helmut4 is driven by a specially crafted streaming engine, visualized in the Stream Designer as a node-based workflow editor.
This "low-code" approach enables users to quickly dive into Helmut4 and create their own workflows.
With over 36 conditions, 259 actions, and 7 output nodes, users have the flexibility to construct any desired workflow.
Each node concludes with a true/success or false/fail path, enabling the adaptation of the workflow and the creation of fail-case conditions without requiring a master's degree in programming.
Stream Execution and Timeouts
By default, every stream has a maximum runtime of 60 seconds. This limit is intended to stop streams that may have entered a hanging state or are simply taking too long to complete.
This timeout can significantly affect FX streams, as it may cause stream and job information to be collected only partially. As a result, project datasets may be incomplete.
For IO, CO, and HK streams, the execution time can be extended beyond the default limit. For details, refer to the following node: Split Stream Action Node
Stream Host Assignment
Streams can generally be assigned to either the client (the local machine, such as Windows or macOS) or the server (Helmut4 Server).
For FX streams, using the server as the primary host assignment is recommended. This is especially useful in environments where network permissions restrict normal users from accessing certain resources.
For IO, CO, and HK streams, the client should always be used. The client host can be defined either in the profile or through the Job Create Job Action node.
Last updated