Step 4 of 5
Add the inclusive join
~2 min ← Back

Add the inclusive join

After the notifications, the process continues. We need a second inclusive gateway to synchronize: wait for all *activated* paths to complete before moving on.

What to do

  • Drag another inclusive gateway (O diamond) onto the canvas, after all three notification tasks
  • Connect each notification task to this join gateway
  • Connect the join gateway to a new task: "Close launch ticket"

Why we need the join

If the inclusive split activates 2 out of 3 paths, the join waits for exactly those 2 to complete. It ignores the unactivated path entirely.

> 💡 An inclusive join that receives a token from each *active* upstream path is called a "merging inclusive gateway". It's smarter than a parallel join (which always waits for everything).

Interactive BPMN Editor
🎉

Tutorial complete!

You finished Flexible branching with inclusive gateways. Great work — you've learned the fundamentals of BPMN modeling.