This happens very rarely - but we found a way to fix it in the next update
For now a restart should help