Link Intermediate Catch Event
The receiving half of a link pair: the token reappears here after 'jumping' from the matching Link Throw. Double thin circle with an outlined arrow.
Link Events are visual go-tos within one process level: a throw/catch pair with the same name teleports the token, replacing a long sequence-flow line that would cross the whole diagram. They carry no execution semantics beyond the jump.
When to use and avoid
When to use
To keep large diagrams readable by avoiding long crossing connectors.
To continue a flow on another 'row' or page of the same process.
When printing/pagination splits a process across sheets.
When NOT to use
Between different processes or Pools — links only work within the same process level.
As control-flow logic — a link is layout sugar, not a decision or event.
In small diagrams where a direct sequence flow is perfectly readable.
Business example
Continuing the flow on a second row
Open this example in the HEFLO process editor and explore the diagram from the inside.
Open in the HEFLO editor →Step by step
- Row 1 ends at the Link Throw “Continue”.
- The token reappears at the matching Link Catch (highlighted) at the start of row 2 — no connector crosses the diagram.
- Row 2 proceeds to analyze the case.
Differences
Link pair vs Sequence Flow
Semantically identical to a direct sequence flow — the pair exists purely to improve layout. If the line wouldn't hurt readability, prefer the explicit flow.
FAQ
How are pairs matched?
By name within the same process level: a throw named “Continue” jumps to the catch named “Continue”.
Can one throw have several catches (or vice versa)?
Multiple throws may target one catch. One throw with multiple same-named catches is ambiguous — avoid it.