-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
7.9.0, 7.10.0
-
None
-
None
Steps to reproduce
- history level is set to full
- inside a subprocess an error is caught by an catching error boundary event so that an activity instance is waiting in a task followed by the boundary event
- the process instance is modified by starting an activity instance in a task right after the task which has produced the error
- the started activity instance waits
Observed behavior
On querying for the...
- unfinished historic activity instance of the subprocess, the parent activity instance id is null
- running activity instance of the subprocess, the parent activity instance id is not null (corresponds to the process instance id)
Expected behavior
The historic as well as the runtime activity instance of the subprocess should return the same value for the parent activity instance id
Hint
This behavior is not observed if the catching error boundary event is missing
