You repost a post on Bluesky, but the repost counter stays at zero or shows a stale number. This is a known behavior on Bluesky where the displayed repost count does not refresh immediately after you or others repost content. The issue is caused by Bluesky’s caching system, which delays the update of engagement metrics to reduce server load. This article explains why the repost count fails to update and provides workarounds to see the accurate number.
Key Takeaways: Fixing the Stale Repost Counter on Bluesky
- Refresh the feed manually: Pull down on the timeline or tap the feed tab to force a cache refresh and update the repost count.
- Wait 5-10 minutes: Bluesky’s backend caches metrics for a short period. The count corrects itself after this interval without any action.
- Use the web app or another device: The count may update on a different client even if it remains stale on your current device due to local caching.
Why Bluesky Repost Count Does Not Update Immediately
Bluesky uses a distributed architecture built on the AT Protocol. When a post is reposted, the action is recorded on the user’s personal data server called a Personal Data Server. The repost count displayed on a post is not a live tally. Instead, Bluesky aggregates repost events and caches the total for a period of time before pushing the updated number to all clients.
This caching mechanism is designed to reduce the number of database queries and network requests. If every repost triggered an immediate update to the counter, the system would need to process thousands of updates per second for popular posts. Caching batches these updates and refreshes the count every few minutes.
The delay typically lasts between 1 and 10 minutes. In some cases, especially during high traffic periods, the lag can extend to 30 minutes or more. The repost count you see may also differ between the Bluesky mobile app and the web app because each client maintains its own local cache that refreshes independently.
Workarounds to See the Updated Repost Count
Because the delay is by design on the server side, there is no setting to force an immediate update. However, the following workarounds can help you see the correct repost count sooner.
- Manual feed refresh on mobile
Open the Bluesky app and navigate to the Home feed or the feed containing the post. Pull down from the top of the screen until the refresh indicator appears. Release to trigger a network request that fetches the latest cached data from the server. This often brings the repost count up to date. - Manual feed refresh on web
In a desktop browser, click the feed tab name such as Home or Following. Press F5 on Windows or Command+R on Mac to reload the page. Alternatively, click the refresh icon if your browser shows one in the address bar. A full page reload clears the local cache and requests fresh data from Bluesky’s servers. - Switch feeds and return
Tap or click a different feed tab such as Trending or a custom feed, then return to the original feed. This action forces the client to re-render the feed and request updated metrics for posts that are still visible. - Open the post in a new tab or view
Click or tap the post to open its detail view. The detail view often fetches a fresh version of the post including the latest repost count. Close the detail view and check the count on the feed again. - Use the Bluesky web app on a different browser
If you are on the mobile app, try opening the same post on the web version at bsky.app. The web app may have a different cached version that shows the correct count. This is useful when you suspect your mobile app cache is stuck. - Log out and log back in
As a last resort, log out of your Bluesky account on the app or website, then log back in. This clears all local data including cached post metrics. After logging back in, navigate to the post to see the updated repost count.
If Bluesky Still Shows the Wrong Repost Count
Repost count shows zero after you reposted
If you just reposted a post and the counter still shows zero, check that the repost was actually registered. Go to your profile and look for the post in your Reposts or Posts tab. If the post appears with a repost indicator, the action was recorded. The count will update after the caching delay. If the post does not appear, try reposting again. A network error can cause the repost to fail silently.
Repost count differs between mobile and web
Each Bluesky client caches data independently. The mobile app might show a count of 5 while the web app shows 8. This is normal and temporary. The counts will converge once both clients fetch the same cached data from the server. To speed up convergence, perform a manual refresh on the client that shows the lower number.
Repost count never updates after several hours
If the repost count remains unchanged for more than an hour, the post may be affected by a server-side caching bug. In this case, open the post in a private browsing window or on a device that has never opened Bluesky before. A fresh client without local cache will show the most current server data. If the count is still wrong, report the issue to Bluesky support through the app menu: Settings > Help and Feedback > Report a Problem.
Bluesky Repost Count vs Like Count Update Behavior
| Item | Repost Count | Like Count |
|---|---|---|
| Update method | Server-side cache batch | Server-side cache batch |
| Typical delay | 1-10 minutes | 1-10 minutes |
| Client refresh effect | May update count after pull-to-refresh | May update count after pull-to-refresh |
| Local cache impact | Mobile and web can show different counts | Mobile and web can show different counts |
| Workaround reliability | Manual refresh works most of the time | Manual refresh works most of the time |
Both repost and like counts use the same caching system on Bluesky. The behavior and workarounds described in this article apply equally to like counts that appear stuck.
The repost count on Bluesky does not update instantly due to server-side caching that batches metrics updates. You can see the correct count sooner by manually refreshing the feed, switching tabs, or opening the post in a detail view. In most cases, the count corrects itself within 10 minutes without any action. For persistent issues, logging out and back in or using a different browser can force a fresh cache load. If you encounter a count that never updates after an hour, report it to Bluesky support as a potential bug.