Hi Alex,
Sorry for the inconvenience.
We have analyzed your query. We were able to reproduce the issue and we confirm this as a bug and logged a defect report .You can keep track of the bug from the feedback portal below.
The fix will be available in our main release which is scheduled to be rolled out on mid of December 2019.
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.