We identified this bug and it occurs in rare circumstances. We will be patching it very soon. One workaround is to switch to another model (or a new model) temporarily and open the model again, which should avoid the bug. Sorry for the inconvenience and thanks for reporting it!