My thinking was that there was an exception handling and the error message was getting muddled into the conversation. But another commenter debunked me.