This appears to be a known issue that we will address in a future version of MobiControl.

In the meantime, does a browser refresh fix the issue for you?