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

Jan 22, 2020 · 6:10 PM UTC

1