Control

The Control Component manages the execution order of different sections within a flow. It ensures that specific parts of a process do not start until all preceding tasks are completed. This allows synchronization and coordination within complex workflows.

To clarify further, please look the flow bellow:

Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.

Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

• Control.1 component will wait for pending messages in the green flow.
• Control.2 component will wait for pending messages in the blue flow.
• Control.3 component will wait for the pending messages in the orange flow.

A Control component can be configured to look at the entire flow in front of it, even going past other Control components. This however, should rarely be necessary to configure.

note

If a Control component is receiving messages but never outputs a signal, it is typically not a timeout issue. The timeout only determines when the component performs its checks. Most issues arise from missing or incomplete connections between components. Ensure that all components and outputs are properly connected to the control component. Increasing the timeout can slows down the process.

Configuration

The Control component can be configured with the following configuration -

Constraint

There are three types of precedence constraints to configure the control component.

Success = When the flow is finished without any error. (No pending message, 0 error)

Failure = When the flow is finished with 1 or more errors (No pending message, > 1 error)

Complete = When the flow is finished. (No pending message, 0 or > 1 error)

Example: success

Timeout

The timeout, defined in milliseconds, determines how long the control component waits after receiving a message. Following the wait time, if there are no pending message and if the constrains are met, the component proceeds by sending a status message to the next component. If the constraints are not satisfied or there are pending messages, no message is sent, awaiting for the next message to restart the process.

Ignore Components

Sometimes, it may not be desirable to include the pending messages of all components in a control component's sub-flow when checking if a constraint is met. In such situations, you can exclude the pending messages of specific components based on their IDs.

Inspect full graph

Whether or not to look beyond other Control components. This will still only look at components that come before it in the flow.

Inputs | Outputs

Control

Input

Output

00 0 (ilsyzu8w)

The Control component takes one input.

Example: Any data