Does GitKraken immediately invalidate cached OAuth credentials after provider-side token revocation?

Goal

Determine whether GitKraken Desktop immediately stops using cached OAuth credentials for a connected GitHub, GitLab, or Bitbucket account after the token is revoked in the provider, or whether the client keeps using stored credentials until the next explicit sign-out or token refresh.

Constraints and uncertainty

GitKraken maintains its own view of remote-tracking references, and fetch or pull operations update that view. OAuth scopes, credential caching, and re-authentication behavior depend on the provider and GitKraken release. Self-hosted GitLab or Bitbucket Server/Data Center may behave differently from cloud-hosted versions.

Does GitKraken reject cached credentials immediately after provider-side token revocation?

Does the client continue to fetch or push using stored credentials until the user signs out or refreshes the token?

Does behavior differ between cloud-hosted and self-hosted provider instances?