Skip to content
Discussion options

You must be logged in to vote

Hi @surinyach,

This is a known asynchronous caching bug with the GitHub profile engine. It occurs when an achievement is unlocked exclusively via private contributions.

The notification service triggers immediately upon meeting the threshold, but the profile router (?tab=achievements) remains uninitialized and throws a 404 because private events often fail to invalidate the public profile UI cache.

Here is how to force GitHub's backend worker to rebuild your profile index and generate the missing section:

1. Force a Public Cache Recalculation (The Quick Fix)

To trigger the backend achievement job (gh-achievements-worker) to recalculate your account's badges:

  1. Create a temporary public rep…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by surinyach
Comment options

You must be logged in to vote
1 reply
@drrakonov
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Profile Showcase your work on GitHub with a personalized profile, bio, contributions and pinned repositories Welcome 🎉 Used to greet and highlight first-time discussion participants. Welcome to the community! source:ui Discussions created via Community GitHub templates Other Features and Feedback Discussions that fall into "Other" category
3 participants