Refresh the page and make sure you're on v0.4.1.4 (uploaded a couple hours ago). It was a bug in 4.1.3.
