Awesome! Thanks! If you think it will be addressed in the next minor release in a couple weeks, I can work around it until then. If it may be a while, (i.e., a month, or two, or more), is there a way to revert the engine back a minor version to 4.10.0 before it was a problem?
Thanks again for all your help on getting this resolved into the future.