Hi Andreas,
Thanks for your patience.
We have validated your query. We have considered the reported scenario as bug and logged a defect report for this. This fix will be available in our volume 4 release which is scheduled to be rolled out on or before December 15, 2020. We appreciate your patience until then. You can keep track of the bug from the feedback portal below.
The provided feedback link is private, and you need to login to view this feedback.
If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal.
Regards,
Srihari