Hey there, this is indeed unintended behaviour and we're looking into it.
update: should be working as normal now.