We update users Library Bundle eligibility in two ways: on login, and once per day. This results in most users eligibility being accurate. However, there are cases where a user logs in to the platform while not being eligible, but then becomes eligible, which leave them confused - we still say they're blocked, when they've just been unblocked, for example. We don't currently provide users any feedback about why their eligibility might not be up to date, or what they can do to refresh it.
We could provide users with a Refresh button on the homepage, in the Library Bundle box, which would enable them to trigger a bundle eligibility update from OAuth. This would need to be rate limited to avoid a user triggering too many backend data updates.
We discussed also providing further explanatory text, but concluded that having a refresh button should be sufficient. If the eligibility isn't up-to-date, users can simply refresh to update it; further text would be redundant.
Original task description
Follow up from report at https://meta.wikimedia.org/w/index.php?title=User_talk:Xaosflux&oldid=20181194#Side_affects_of_blocks
When a user is blocked on a WMF project and attempts to access the library, they are refused per current configuration.
However, if their block is resolved, the library continues to reject their access. This may be resolved by the user creating a new session by logging out and logging back in - possible bad caching in this application.
Users without active blocks should not be denied access - the application should always validate current status.