Sourcetree shows generic Authentication failed error for expired personal access token

When a personal access token (PAT) used for HTTPS authentication in Atlassian Sourcetree expires, the application shows a generic Authentication failed dialog without indicating that the credential has expired.

The goal is to determine whether Sourcetree can be configured or extended to surface a more specific error (token expired) so users can take timely action, given that Sourcetree relies on the operating system's keychain or Git credential helper and does not automatically refresh OAuth tokens.

Is there a setting, environment variable, or credential‑helper behavior that triggers a distinct error message for expired PATs? Does Sourcetree expose any internal log or diagnostic output that differentiates expiration from other authentication failures? Are there known work‑arounds that preserve least‑privilege scopes while providing clearer expiry feedback?