It is probably a simple update to the query that will fix the problem. However there may also be an underlying database integrity issue I'd like to investigate.
The support incident will remain open. Please update it if you run into this problem again and we can work with you to diagnose it and find a permanent fix so it won't happen again.