Howdy Everyone!
I’m glad to hear a workaround was found. I did pass this up and we are seeing the same thing. A bug report has been opened on this and we are looking into it.
No ETA right now but I’ll update this thread if I hear anything or if we need any additional information.