Error with timestamp displayed only

Problem should not occur if you go back to 2018.2.x for now.