Fork

Intro

A fork splits a process path into parallel paths that run simultaneously. It matters because parallelization can reduce cycle time and increase throughput.

Key points:

• Represented by multiple outgoing sequence flows or a parallel gateway.
• Requires careful synchronization when paths merge.
• Common use cases: concurrent checks (BPM), parallel jobs (Apps/Tech), multi‑channel notifications.
• Pitfall: race conditions or missing joins causing incomplete processing.

Examples:

• Running credit, fraud, and KYC checks in parallel.
• Launching batch jobs across workers simultaneously.
• Sending notifications via email and SMS at the same time.

In practice:

Use explicit join gateways and define completion rules to avoid deadlocks and partial finishes.

Related terms: parallel-gateway; join; sequence-flow

FAQs:

Q: Is a fork the same as an inclusive gateway?
A: No; parallel gateways start all paths, inclusive gateways start selected paths.

Q: How do I merge parallel paths?
A: With a parallel gateway or defined synchronization logic.

‍