it's been happening for some time and is application related. It's a different issue than what's happening with the API today. I'll wait 'til gc.com resolves their issue with the API and reproduce the error again and provide more details.
↧