Thank you all for the reports! I’ve captured all of the information from this update. To help keep things organized, I’ve opened a new thread following our latest build:
The main fixes for this particular issue should be coming in the May build, but I will continue collecting information about the issue in the new thread to ensure we have approached it from every angle.