Strange, maybe there was a bug in a cached version or something... or gremlins!

Glad to hear it's working in this new version though. If it happens again we'll debug it a bit deeper and hopefully I'll be able to reproduce it.