Hi Marcus,
We can reproduce the reported issue and we have logged bug report for this. The fix for the reported issue will be included in our Volume 1 SP1 release which is scheduled to be rolled out on mid of May 2020. We appreciate your patience until then.
You can now track the status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Note: The provided feedback link is private, and you need to login to view this feedback.
Regards,
Ramya S