Update: Our engineers confirmed the bug is back and are working on fixing it again. I don’t know exactly why the previous fix was taken out - but usually when that sort of thing happens it’s because it caused an unforeseen issue and we have to temporarily remove it to tinker with it some more.