We have evaluated this issue and determined it’s likely a bug. We are prioritizing it along with other potential code changes and will update this article when we have more information.