Platform
Desktop - Windows
The Problem
When a configured Remote Sync session expires:
- The top banner Reconnect action only opens the User Profile panel and does not open the re-authentication dialog.
- The panel Reconnect flow can close as successful even when the remote server did not return a new JWT.
- Sync Now consumes the main-process status without showing success or failure feedback.
The UI therefore returns to Sign-in expired with no actionable error, making every action appear unresponsive.
Expected Behavior
- Both Reconnect actions open the login dialog for the configured server directly.
- Re-authentication remains open and displays an error if no token is returned or the token is rejected.
- Sync Now displays an explicit success or failure toast.
Additional Context
Reproduced against a configured remote server after the persisted remote JWT expired.
Platform
Desktop - Windows
The Problem
When a configured Remote Sync session expires:
The UI therefore returns to
Sign-in expiredwith no actionable error, making every action appear unresponsive.Expected Behavior
Additional Context
Reproduced against a configured remote server after the persisted remote JWT expired.