the correct fix for what you observed is a recovery token to re-sync settings from the sync API