Thanks for your response Chris.
You are right, incongruent was a better descriptor of the issue. We were also getting tags with no closing tags, tags with multiple values inside them, etc. It changed around the the same time the response changed from 200 to 200 OK.
It appears the engineering group has resolved the issue, and it's back to reporting 0 instead of an empty response. I also haven't had any unclosed tags, multiple values, server timeouts, or server returning empty responses today.
I like the change of returning the blasts in order of most recent first. Just wish there was better change notification.
Thanks again,
Stacey