Thanks for your patience. We’ve now pushed some changes intended to address this issue. Please find further details here: