As a follow up, this seems to have helped, as our user reports that this has not happened again since we made this change to their settings.
