Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The StackExchange Inbox tab (not the top left inbox link but the dedicated page) has been stuck on older messages for around 2 around 4 days now.

Scroll down from top left Inbox to the bottom to "See All". This link sometimes shows as "more inbox messages …"

enter image description here

which takes you to the page below. Note: you can get to this Inbox page from Network Profile > Inbox as well

Mine is out of sync by about 40 messages or 12 days. In case that helps.

enter image description here

share|improve this question
Wow, I've never notice the "See all" link, and don't see it currently (IE9). – Lance Roberts Sep 22 '11 at 5:27
@Lance: I've tried IE8 and FF5 and can "See All". Besides you can get to this Inbox page from Network Profile > Inbox too. – JoseK Sep 22 '11 at 5:30
@Lance: Did you scroll down to the bottom of the inbox? There's the link. – JoseK Sep 22 '11 at 5:33
OK, I see it after scrolling, but it says "more inbox messages ...". My last message was Sep 14th it says, so yeh, I'm missing a weeks worth. – Lance Roberts Sep 22 '11 at 5:37
up vote 4 down vote accepted

There was an ordering issue here, your new items were actually on page 2, 3, 4, or 5 (depending on how many you had). This is now fixed.

In-depth why, because we care <3:
We actually store your inbox in 2 places, your most recent items are in redis, and your older ones are in SQL. After a small delay a background process culls them from redis to SQL.

Actually after a minute or two usually, all your items are in both places...but since redis may still be changing, or have a deletion that's not yet persisted, etc...we need to construct the overall inbox that shows from both sources.

To do this, we take the items from redis (observing the earliest date) and the items from SQL (any before the minimum redis date), then combine them in code via .Union(), this was happening backwards in some cases.

In addition to that, the API on the backend for has a page size 5x larger than what is shown on (meaning loads 5 pages at once when fetching)...combine these two and you see how your new items were appearing at the end of the first API page, which translated to anywhere from page 1-5 on, depending on how many new items you had.

share|improve this answer
didnt expect this to be fixed on the weekend, cheers – JoseK Sep 24 '11 at 16:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .