Thanks for the additional information! I’ve added your comments/reference to the internal bug tracking this issue.