# NousResearch/hermes-agent · Spotify invalid_grant refresh token expiry handling

## Open now

- Nothing open on GitHub.

A bug report and related fix and documentation work addressing how the Spotify integration handles expired refresh tokens that return invalid_grant errors. The work covers error handling, a quarantine mechanism, and re-authentication flow documentation and tests.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #48381: \[BUG\] Spotify refresh tokens expire after 6 months: no re-auth flow on invalid_grant

## Prior & competing PRs

- **#48396: fix(spotify): handle invalid_grant refresh token expiry with quaranti…**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#28155`
- **#48409: docs+test(spotify): add re-auth cycle docs and client-level invalid_grant test**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#49944`

## Fix status

- No merged fix on record.
- Subsystem: `agent`