What should happen when a smart-glasses account disconnects?
The app should stop using that connection, clear or label dependent state and explain which features remain available. Reconnection should not quietly restore stale requests or use the wrong account's content.
Treat account state as part of the interaction
Cancel unfinished work tied to the disconnected account and avoid presenting its old results as current. If some saved local content remains available, label it accordingly. Otherwise the wearer can mistake a cached display for a live service connection.
Imagine disconnecting a calendar account while a reminder request is pending. A late response should not reappear as though the account were still active. On reconnect, the application should obtain current state through its supported flow instead of replaying a queue whose context has changed.