Thanks for getting in touch! I’m sorry you’re hitting this unexpected issue! I have been able to reproduce it in my local instance running 3.15.7. I’ve raised the following issue to investigate it further and get it resolved.
Thanks for bringing this to our attention, and I’m sorry about the confusion caused by it.