The owner of this thread was seeing the same error, and it was due to multiple triggers being received. Might be related.