Developer Reference· 9 min read· Updated November 2026
Model Validation Rules
Next releaseThe rules already include those of the next release of Flower BPM, for example the checks of link, loop, message and signal elements.
The modeler validates a model when you click Validate and before Publish. Each problem is shown on its element with a message.
- Error: the model is not ready to publish. Fix it first.
- Warning: the model can be published, but an element behaves differently than you may expect, or does nothing.
The table lists every rule of the validator with its code, level, and message. In a message, … stands for a part that the validator fills in, such as the name of the element.
Generated from bit.flower master by util/generate-specs.mjs. Do not edit this section by hand.
16 errors and 31 warnings.
| Code | Level | Message | What to do |
|---|---|---|---|
| – | Error | Start nodes are missing | Add a start event to the process. |
CALL_ACTIVITY_NOT_MAPPED | Error | The space and work type of the call activity are not part of the Jira work type mapping: … (… / …) | Map the space and work type of the call activity to the model it should run (Flower Settings, Jira work type mapping), or select a space and work type that are mapped. |
CALL_ACTIVITY_WITHOUT_JIRA_SETTINGS | Error | A call activity needs its own space and work type from the Jira work type mapping, they are not inherited: … | Select a space and a work type on the call activity: they decide which model runs as the sub-process and are not taken from the lane or the defaults. |
END_NODE_MISSING | Error | End nodes are missing | Add an end event, so that the process instance is resolved when the process has run through. |
MANDATORY_FIELD_NOT_ALLOWED | Error | Mandatory fields are not allowed: … | Make the named fields optional in the field configuration of the work type, or use another work type: the engine creates work items without them and Jira would refuse the work item. |
ONLY_ONE_TIMER_ALLOWED | Error | Only one timer boundary event allowed per activity: … | Keep one timer boundary event per activity. |
PROCESS_START_BEFORE_START_NODE | Error | Process must be terminated by an end node. No previous nodes are allowed. | Remove the flow that leads into the start event: a start event has no incoming flow. |
PROCESS_START_WITHOUT_START_NODE | Error | Process must be started by a start node. | Connect the element with an incoming flow, or remove it: every element except start events and boundary events needs one. |
PROCESS_TERMINATION_AFTER_END_NODE | Error | Process must be terminated by an end node. No further nodes are allowed. | Remove the flow that leaves the end event: nothing follows an end event. |
PROJECT_NOT_EXIST | Error | Project does not exist at this Jira instance: … | Select a space that exists on this Jira site. Models imported from another site often name spaces of that site. |
SUBPROCESS_CYCLE | Error | The sub process calls itself, directly or through other models: … | Break the cycle: a model must not call itself, also not through other models that it calls. |
SUBPROCESS_NOT_RELATED | Error | Subprocess not related | Select the model that the sub-process should run. |
TIMER_CYCLE_NOT_SUPPORTED | Error | The timer start event ”…” has a cycle: Flower starts a process instance only once. For repeating starts, let a scheduled rule of Jira Automation create a work item of a mapped work type. / The timer event ”…” has a cycle: it fires only once in the flow. Use a duration or a date. | Use a duration (for example P3D) or a date instead of a cycle. For repeating starts, let a scheduled rule of Jira Automation create a work item of a mapped work type. |
TOO_MANY_OUTGOING_TRANSITIONS_AT_START_NODE | Error | Currently only one outgoing transition is allowed at a start node | Leave the start event with one flow. To start several branches, put a parallel gateway after it. |
TRANSITION_DOUBLICATED | Error | Transition doublicated | Delete one of the two flows between the same elements. |
WRONG_GATEWAY_TRANSITION_COUNT | Error | The number of incoming transitions (…) at the join gateway …) must be the same as the number of outgoing transitions (…) at the split gateway …. | Give the joining gateway as many incoming flows as the splitting gateway has outgoing flows, so that the join waits for every branch. |
ACTIVITY_WITHOUT_NAME | Warning | Activity without name | Name the activity: its name becomes the summary of the work item. |
BOUNDARY_EVENT_NOT_SUPPORTED | Warning | Flower does not execute the boundary event ”…” (…): it never fires. | Use a boundary event type that is executed (timer, error, escalation, conditional, message, signal), or remove it. |
BOUNDARY_EVENT_WITHOUT_DEFINITION | Warning | This boundary event has no event definition (timer, message, …) and has no effect. | Choose the type of the boundary event (timer, error, escalation, conditional, message, signal), or remove it. |
CONDITIONAL_BOUNDARY_WITHOUT_CONDITION | Warning | The conditional boundary event ”…” has no condition: it never fires. | Enter an expression in the group Condition of the event, or check a status or resolution of the work item there. |
CONDITIONAL_EVENT_WITHOUT_CONDITION | Warning | The conditional event ”…” has no condition: the process waits there forever. Enter the condition in the group Condition. | Enter an expression in the group Condition of the event. |
ELEMENT_NOT_SUPPORTED | Warning | Flower does not execute the event sub-process ”…”: it never starts. Flower starts event sub-processes with a conditional, timer, error, message, signal or escalation start event; a process with an event start event must have only that one start event. | Give the event sub-process a start event Flower executes (conditional, timer, error, escalation, message, signal), keep at most one event start event of the process, and put the event sub-process at the top of the process, not inside an embedded sub-process. |
ELEMENT_PASSED | Warning | Flower does not execute the … ”…”: the process passes it without doing anything. Tick “Wait for Jira Automation” (the task starts a rule and waits for it), or use a task (a work item). / Flower does not run the script of the script task ”…” (no code of a model runs on the server): the process passes it without doing anything. Tick “Wait for Jira Automation” to let a rule do the work. | Tick Wait for Jira Automation on the task: a rule of Jira Automation does the work and reports it done. Otherwise use a task (it becomes a work item). |
ELEMENT_RUNS_AS_INCLUSIVE | Warning | The complex gateway ”…” runs like an inclusive gateway: every outgoing flow whose condition is true is taken, the activation condition is not evaluated. | Nothing to do if every flow whose condition is true should be taken. Otherwise use an inclusive or an exclusive gateway. |
ELEMENT_RUNS_AS_SUBPROCESS | Warning | The … ”…” runs like an embedded sub-process: its tasks become work items, … | Nothing to do if the element should run like an embedded sub-process. Transactions and ad-hoc behaviour are not executed. |
ELEMENT_RUNS_ONCE | Warning | Flower runs ”…” once: multi-instance markers are not executed. / Flower runs ”…” once: loop markers run on tasks, user tasks, manual tasks and automated tasks that wait for Jira Automation (not on receive tasks, other automated tasks, sub-processes and call activities). | For a loop, put the loop marker on a task (also a user, manual, or automated task with Wait for Jira Automation). For one run per item of a list, see Once per Item of a List in the docs of markers. |
ERROR_BOUNDARY_WITHOUT_STATUS | Warning | The error boundary event ”…” has no Jira status: it never fires. Select the status in the group Error. | Select the Jira status in the group Error of the event. The workflow of the work type must offer it. |
ESCALATION_BOUNDARY_WITHOUT_STATUS | Warning | The escalation boundary event ”…” has no Jira status: it never fires. Select the status in the group Escalation. | Select the Jira status in the group Escalation of the event. The workflow of the work type must offer it. |
EXPRESSION_ERROR | Warning | Invalid timer expression at: … | Write the timer value in ISO 8601, for example P3D for three days or a date such as 2026-12-31. |
EXPRESSION_REFUSED | Warning | The … of ”…” cannot be evaluated: … | Correct the expression: the message names the problem. See Expressions for what an expression can do. |
LANE_WITHOUT_NAME | Warning | Lane without name | Name the lane after the role or team it stands for. |
LINK_WITHOUT_CATCH | Warning | The link throw event ”…” has no link catch event with the link name ”…” in its process: the process stops there. | Give a link catch event in the same process the link name of this throw event, or correct the name. |
LINK_WITHOUT_THROW | Warning | The link catch event ”…” is not reached: no link throw event with the link name ”…” in its process. | Give a link throw event in the same process this link name, or remove the catch event. |
LOOP_WITHOUT_CONDITION | Warning | The loop marker of ”…” has no loop condition: Flower runs the task once. Choose a status or resolution of the work item in the group Loop, or give it a condition, e.g. ${cur.fields.resolution != ‘Done’} (the task runs again as long as it is true). | Check a status or resolution in the group Loop, or enter a loop condition; remove the marker if the task runs once. |
MESSAGE_FLOW_NOT_DELIVERED | Warning | This message flow …: the engine does not deliver it. | Let the message flow go from a throw event, send task or end event of one pool to a catch event, receive task, start event or boundary event of another pool of the same model. |
MESSAGE_WITHOUT_NAME | Warning | ”…” waits for a message without a name: select or create a message with a name. The name is what a comment “@FlowerBPM <name>” or Jira Automation sends. | Select or create a message with a name: the sender uses it (@FlowerBPM <name>, Jira Automation, REST API). |
MISSING_EXPRESSION | Warning | Missing expression at exclusive gateway: … | Enter an expression on the flow, check a status or resolution of the work item in the group Condition, or make the flow the default flow of the gateway. |
NO_DEFAULT_TRANSITION | Warning | The gateway has no default flow: if no condition is true, the process stops with an error comment: … | Mark one outgoing flow of the gateway as the default flow: it is taken when no condition is true, also when a field is empty. |
PROCESS_TERMINATION_WITHOUT_END_NODE | Warning | This path does not end in an end event. The process runs to this point and stops; the process instance is resolved only if another branch reaches an end event. | Lead the path to an end event. |
REPEATING_TIMER_INTERRUPTING | Warning | A repeating timer needs a non-interrupting boundary event, an interrupting one fires only once and cancels the activity: … | Make the timer boundary event non-interrupting, or use a duration instead of a cycle. |
SCRIPT_CONDITION_NOT_RUN | Warning | The script condition of ”…” is not executed (script conditions are not executed, use an expression): the condition is always false. | Replace the script with an expression, for example ${cur.fields.resolution == ‘Done’}. |
SIGNAL_WITHOUT_NAME | Warning | ”…” has a signal without a name: select or create a signal with a name. Signals are matched by their name. | Select or create a signal with a name: waiting process instances are found by it. |
SUBPROCESS_MODEL_NOT_AVAILABLE | Warning | The model of the sub process cannot be loaded, is it published? … | Publish the model that the call activity runs, or map the work type to a published model. |
SUBTASK_OTHER_SPACE | Warning | The work type of ”…” is a sub-task type, but its space (…) is not the space of the process instance (…): it is created with the default work type. | Use the space of the process instance for activities with a sub-task type, or a work type that is not a sub-task. |
SUBTASK_PROCESS_INSTANCE_IS_SUBTASK | Warning | The work type of the process instance is a sub-task type: Jira does not allow sub-tasks below a sub-task, the activities with a sub-task type are created with the default work type. | Use a work type that is not a sub-task for the process instance, or standard work types for its activities. |
TASK_USES_MAPPED_WORK_TYPE | Warning | The work type of this activity is part of the Jira work type mapping, so its work item would start a process: … (… / …). Use a call activity to start a sub process. | Use another work type for the activity, or a call activity if its work item should start a sub-process. |
WEBHOOK_NOT_ON_FORGE | Warning | ”…” calls a web service: the Forge app does not call URLs. Set the request type of the event to Jira Automation (a rule can call the web service). | Set the request type of the event to Jira Automation; the rule can call the web service (Send web request). Forge only. |
The modeler can also show modeling hints of bpmnlint while you draw. They are hints on the style of the diagram, separate from these rules.
Last updated on