Weird cancellation-scope behaviour (Java SDK)

This looks as same issue discussed in this recent post. Also see opened issue here.

Workaround as discussed there was to wait for child workflow execution to start inside the cancellation scope.