Key takeaway: BPMN modeling errors are more than notation inaccuracies. An incorrectly chosen gateway, a missing exception path, or incorrectly connected participants can cause a case to stall, a task to start twice, or responsibilities to remain unclear. A good model is valid, understandable from a business perspective, and implementable.
This installment of the “BPMN 2.0 in Practice” series presents ten common errors through a case management example: an application arrives, we check the documents, request missing information if necessary, and then make a decision. At each point, we distinguish between the notation rule, the operational consequence, and the fix.
Practical focus: This series is not a complete BPMN 2.0 reference manual—the official notation set is far broader, and here we focus on the most essential elements and practical workflows used in everyday operations.
Participants and responsibilities: where does the process boundary lie?
1. A sequence flow crosses between two pools
The error: the customer and the organization handling the case appear in separate pools, yet a solid arrow connects their activities. A sequence flow shows the execution order within a process, so it cannot cross a pool boundary. Communication between separate participants is represented by a message flow.
The fix: represent the sending and receiving of the application with a message flow. Otherwise, the diagram may suggest that the organization directly controls the customer's work. When designing case management in xFLOWer, document waiting for an external response separately from internal task execution.
2. A message flow connects two internal lanes
The error: the case handler and the manager work in two lanes within the same pool, yet a message flow connects them. A lane helps organize responsibilities; it is not a separate participant in itself. Within a pool, a sequence flow can cross a lane boundary, but a message flow cannot be used as an internal connection.
The fix: connect managerial approval using a sequence flow, and define the task assignee separately. A lane name is not an executable authorization rule: clarify the role, substitution arrangements, and who can view the case data.
Activities and events: make the work and lifecycle clear
3. The activity name does not explain what happens
The error: the task is named “Document” or “Case handling.” This is not necessarily a violation of BPMN rules, but it makes the model ambiguous from a business perspective. It is unclear whether document uploading, checking, or archiving is expected, so the acceptance criteria are also unclear.
The fix: use an action and an object: “Check attachments.” Specify the input and the outcome as well, such as “complete” or “additional information required.” In a case management implementation, the appropriate form, required field, and completion condition can be assigned to this task. A task is well defined when two case handlers understand it in the same way.
4. Start and end events are connected in the wrong direction
The error: a loop-back arrow enters the start event, or another task starts from the end event. A start event cannot have an incoming sequence flow, and an end event cannot have an outgoing sequence flow. The correction loop must therefore not lead back to the start event.
The fix: after the missing information has been supplied, return to the appropriate checking activity. Clarify what completion means as well: a normal end event ends the execution path that reaches it, not necessarily all parallel paths. A terminate end event, which terminates the entire scope, behaves differently.
Gateways: the wrong choice causes deadlocks or extra work
5. An exclusive split is followed by a parallel join
The error: the decision leads to either approval or rejection, and the two paths then converge at a parallel gateway. An exclusive split activates only one path, while a parallel join waits for every incoming branch to complete. In a simple structure like this, the case stalls.
The fix: use an exclusive gateway to merge alternative paths. A parallel split is appropriate when, for example, both legal and financial reviews must be performed. When choosing how to join paths, always ask: which branches have started, and which must finish before we proceed?
6. The exclusive gateway conditions overlap or are incomplete
The error: one branch has the condition “amount at least 100 000,” while the other has “amount at most 100 000.” At the threshold, both are true. In other cases, neither condition is met and there is no default branch. The model therefore fails to describe the business decision unambiguously.
The fix: use mutually exclusive conditions, such as “below 100 000” and “100 000 or above.” Handle missing data as well, and provide a default branch if necessary. Test values below, equal to, and above the threshold, as well as an empty field.
Waiting and exceptions: include more than just the ideal path
7. A data-based decision is modeled instead of an event-based gateway
The error: the “Customer responds or the deadline expires” scenario is represented as though the response were already known data. In fact, future events are competing here. An event-based gateway can be followed by appropriate intermediate catch events or receive tasks, not arbitrary work steps.
Fix: use a message catch event on one path of a standard exclusive event-based gateway and a timer event on the other. The first event to occur determines how the process continues. If the response is already available and exactly one subsequent path must be selected based on its content, use a data-based exclusive gateway.
8. Failing to distinguish between interrupting and non-interrupting events
The error: all deadline events are modeled in the same way, even though a reminder and a task interruption are not the same. An interrupting boundary event attached to an activity stops that activity; the non-interrupting version starts an additional branch alongside it.
Fix: generally, choose non-interrupting behavior for reminders and interrupting behavior for actual termination. Define the rule in business terms as well: can the case handler continue working after the deadline? When configuring xFLOWer case management, align this with the task status and subsequent permissions.
From model to execution: two common structural mistakes
9. Putting every detail into a single diagram
The error: the main process includes management decisions, individual field validations, and every technical operation. Overcrowding obscures responsibilities and incorrect paths. This is primarily a readability issue, but it also makes business review significantly harder.
Fix: divide the model into meaningful subprocesses, such as “Intake,” “Substantive review,” and “Decision notification.” Place detailed rules at the appropriate level. At subprocess boundaries, however, keep inputs, outputs, ownership, and exception handling clearly defined.
10. Assuming a valid diagram is automatically executable
The error: the team declares the process complete because the diagram uses correct notation. Execution requires the details necessary for that particular process to operate, such as task assignments, branching conditions, or external system connections. The target system’s supported BPMN elements and execution semantics also matter.
Fix: for implementation in xFLOWer, map the model to the behavior that needs to be configured. Do not assume automatic import or full support for all elements without verification. Test the standard case, requests for missing information, rejection, missed deadlines, and integration failures.
Correction table and pre-handover checks
Use the table for a quick check. It does not replace a model walkthrough: at every decision, trace which branches are active and where the process waits.
| Error | Typical consequence | Fix |
|---|---|---|
| 1. Sequence flow crossing a pool boundary | Incorrect control flow connection | Message flow between participants |
| 2. Internal message flow | Unclear handover of responsibility | Sequence flow and task assignment |
| 3. Vague task name | Inconsistent interpretations | Action, object, outcome |
| 4. Incorrect event connection | Incorrect lifecycle | Valid start and completion |
| 5. Incorrect merging | Process stalls | Gateway appropriate for the active branches |
| 6. Incorrect conditions | Uncertain path selection | Mutually exclusive conditions, boundary value testing |
| 7. Incorrect waiting behavior | Incorrect continuation logic | Separating events from data-based decisions |
| 8. Incorrect interruption | A task that stops or remains active | Deliberate selection of boundary events |
| 9. Overcrowded diagram | Errors that remain hidden | Breaking the process down into subprocesses |
| 10. Missing execution details | Implementation gaps | Configuration mapping and testing |
Complete three steps before handover:
- Notation check: review connections, events, and gateways.
- Business walkthrough: trace specific cases with the participants.
- Execution test: test data, permissions, deadlines, and exceptions.
Summary: a good model is a verifiable agreement on how work is performed
Preventing BPMN modeling errors starts with examining notation rules and business consequences together. The goal is not a more complex diagram, but clear responsibilities, correct routing, and manageable exceptions.
Further articles on this topic: BPMN 2.0 Elements Explained with Examples; Exclusive, Parallel, and Event-Based Gateways: When Should You Use Each?; BPMN vs. Flowcharts vs. UML Activity Diagrams; and How Does a BPMN Diagram Become an Executable Process?
Would you like to check these points against your own case management process? Schedule a discussion with the xFLOWer team and bring a specific process diagram, along with its decision rules, responsibilities, and deadlines. These provide a useful starting point for an expert review of the implementation.
This article is part of our comprehensive guide: BPMN 2.0 in Practice: A Complete Guide from Modeling to a Working Process
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
