BPMN2 — Page 26, Normal Flow row of Table 7.2 - Modeling activities that do not complete before process completion

There are activities that are never ended - that is they have no natural completion, but are
terminated only when the process itself is terminated. Monitoring activities are like that.
If an activity is started, and there is never a conclusion of that activity, then this should be
indicated by having no outbound arrow from the activity. This activity is concluded only
by the termination of the process as a whole. For example, and process may have a main
thread, but also split early and start a "monitoring" activity. This monitoring activity is
designed to stay active until the process is concluded for some other reason. There is no
way for the assignee of the activity to say "I am done monitoring this process" without
the process itself being terminated. Since there is no "natural" end of the activity, there
should be no arrow coming out of the activity node. I am not sure if this is a requirement
of the spec, but there is a common perception that it is a requirement, that all activities
have an outbound arrow coming out of it.

This request is that the spec include a statement that it is explicitly OK to not have an
arrow out of an activity that has no natural end to its execution.

If this is not agreed, the spec needs to explain how to model such activities

Close this issue as a duplicate.
The resolution of issue 14351 will resolve this issue
Disposition: Duplicate