Hello,
I reproduced this behavior and have submitted a development issue.
This issue has been resolved by the latest Service Release as of the date of this post.