Investigate refresh behavior of old access tokens
I'm going to dig into and try to fully reproduce what Zhongcan ran into last week. I suspect the problem is that his Galaxy session was older than 30 days. 30 days is currently the threshold where we won't attempt to refresh tokens older than this. I can briefly reduce the threshold to zero days in the test instance and check the refresh behavior.
issue