last time something similar happened to me, it was an user event deployed on the record. Which for some reason it was not showing in the stack trace