Hello,
I have a process with a subprocess which itself has an event subprocess:
When the subprocess stops because of incidents occurred - I expect it to remain stuck there until those incidents are resolved and tasks given a chance to retry.
Instead, when an event subprocess is started with an event “Add new message” - then the process instance finishes “NOTIFYING”, then loops through “NOTIFIED” and “SCHEDULED” back to “NOTIFYING” - I can see those transitions logged. How can this happen?
According to the BPMN description Camunda Platform 7 documentation | docs.camunda.org
When an event subprocess is ended, either the current scope is ended (in case of an interrupting event subprocess), or the concurrent execution spawned for the non-interrupting subprocess is ended.
So I expect it to just end and not go anywhere further.
Is this a bug or me not understanding BPMN properly?