The same step, drawn twice
A gym takes sign-ups in two ways: online, or in person at the front desk. The paperwork differs, but either way the new member ends up with the same card. Here is the drawing most people make first, with the card step copied onto each branch.
On the day it is drawn, nothing is wrong with it. It reads correctly and the Grid accepts it. The trouble arrives with the first change. The gym starts printing a photo on its cards, and someone edits the step on the branch they happen to be looking at, so one copy now says "Issue card with photo". The diagram now says online members get a photo and front-desk members do not. Is that a rule or an oversight? The drawing cannot answer, because two separate boxes are allowed to differ on purpose.
So you delete one copy and drag the other branch's edge onto the box that remains. The Grid refuses: Issue card already has its maximum of 1 incoming connection. A Process, a Decision and the other ordinary steps take one incoming edge, and the limit counts every edge arriving at the node, whichever port it uses. Paths can meet only at a node built for it, so a meeting is a symbol you can see, not two arrows that happen to land on the same box.
One card step, and a place to meet
A Merge is that node: it accepts up to four inputs and emits a single output. Both branches go into the Merge, and only the Merge goes into Issue card.
Now the photo goes into one box, once, for everybody. Notice the ports too: Check web form enters at in-1 and Desk form at in-2. Wire both branches into the same input port and the edges stack on top of each other, so use distinct ports and a reader can count the inputs.
Convergence is for a step that really is the same step. If online members get a virtual card and front-desk members a plastic one, those are two jobs, and two differently titled boxes are the right drawing.
What a Merge leaves unsaid
A Merge rejoins paths and states no waiting, so a flow that must wait for every branch needs a Summing Junction or a Parallel Gateway; Junctions: Or & Summing and Gateways: parallel, inclusive & event cover them. The gym has nothing to wait for, because its Decision sends each sign-up down one branch. Branches running side by side are the subject of Split & parallelism, whose diagrams rejoin them on a Summing Junction, while its two Challenges give you a Merge instead.
Merge is the generic choice, not the only one; Junctions: Or & Summing says what an Or adds to it. The same refusal also appears when a flow goes back to an earlier step, because the way back is a second incoming edge, and Loops & retries draws that re-entry through a Merge.
A fifth way in
The gym adds phone sign-ups, a partner app and a corporate plan, and the fifth edge arriving at the Merge gets the same answer: Merge already has its maximum of 4 incoming connections. Feed one Merge's output into an input of a second Merge: the first takes four paths and the second takes that output plus three more, seven in all.
Allowed or rejected, one response
API Rate-Limit Decision Flow requires this in so many words: merge the allowed and rejected paths before the final response. Draw the final response once, after a Merge, not a copy on each branch. Retry with Backoff Flow puts the Merge somewhere else: route both the first attempt and every retry through the same Merge before the call step, so the call step depends on exactly one node however many retries happen.