The Inbound Flow Link component can be used together with the Outbound Flow Link component to connect flows with each other. This enables you to split up bigger integrations in several reusable flows.
This component is meant to be the first component in a flow, because it acts as a consumer. It consumes messages that are sent by one or more Outbound Flow Link components that are located in other flows.
This component has only one configuration option: Flow link type
Flow link type
This option determines how the messages are handled by the component. By default
the option is set to
Parallel which means that multiple messages can be received
at the same time. This also means that you can't expect messages to be processed
in a specific order, but this improves performance.
The other option
Sequential is only recommended to be used when you really need
the messages to be received in the order that they are sent by the
Outbound Flow Link component. This option will cause higher
load on the system when processing a lot of data.
You can't sent messages to this component with an
Outbound Flow Link component that has a different
Flow link type. For example: a sequential
Outbound Flow Link component can't send messages to a
parallel Inbound flow link component.
In the properties modal of this component you can also see all flows that target
it for sending messages. When there are no
Outbound Flow Link components that target it you will see
the following message:
There are no connected flows. When there are one or more
Outbound Flow Link components that target this component
then you will see a list of flows in which these are located. You can navigate to
these flows easily by clicking on the name.
Take note that we can only show connected flows that have the connected Outbound Flow Link component in the draft version of the flow. So it can be possible that you don't see a flow in this list while you expect it to be there.
When some flows have a Flow link type mismatch then they become red and an error message will also be displayed below the list.
- To see the full origin/target flow chain in the tracing, all connected flows should have tracing enabled.