Usecase is: we skip timers by cancelling the timer activity and start after the timer activity the process again via ProcessModification. While I saw, that there was a bug in some older versions where the parent of the call activity did not go further if a modification took place in the call activity itself: https://jira.camunda.com/browse/CAM-7165
we use camunda 7.8.0 - could it be, that the problem was fixed later and not in 7.8.0 as mentioned in the ticket. I get exactly the same behaviour in my scenario.