@ooswald Sorry to hear about that! The problem you've described was a temporary issue, and it should be working normally again now. ^JR