I think @al3xicon encountered a situation like that. It ended up being a really strange defect that only affected a single field on a custom record.