Has this been resolved? This is happening to me in production now on code that worked for quite a while. there must be a data condition/threshhold that causes this behavior.