Thanks Will. Salesforce data rules should have prevented this from happening, but it’s been known to occur very rarely: https://developer.salesforce.com/forums/?id=906F000000091hDIAQ. Unfortunately, there’s not much we’d be able to do to prevent this (since it’s supposed to be guarded against at the database level). Your steps to repair it were exactly right… Pat beat us to the punch, but that’s why he’s a community champion. :)
