So this went away the next day after a patch was released.....However, it's back again. Same exact bug.