DataSpell remote Jupyter token expiration failing to prompt refresh

DataSpell connects to remote Jupyter servers using authentication tokens or password-based methods. However, the interface does not currently expose the specific permission scopes for these connections, raising concerns regarding least-privilege access enforcement.

When a remote Jupyter token expires during runtime, the IDE often reports a generic connection error rather than triggering a re-authentication prompt. This behavior appears inconsistent between local and remote kernels, and it is unclear if the internal credential store tracks expiration metadata or simply relies on the stored string until a silent failure occurs.

How does DataSpell distinguish between a network-level timeout and an expired authentication token? Is there a mechanism to force a credential refresh workflow for stored remote Jupyter connections without manually deleting the connection profile?