Discrepancy between Retrievability Stat in Card Info vs Card Browser

Simple issue - when I add “Retrievability” field to the card browser, I’ll get one value, but very often, if I actually inspect the cards and go to the Card Details (with date added, first review, etc.), I’ll get a completely different value.

The one on the card seems correct intuitively (on my examples), but how do I get THAT one in my Browser?

Running Anki 25.02.1 on macOS, tried in Safe Mode. It happens only with cards that were shifted around decks, and which were subject to using of the “Postpone Cards” Add-on (not the FSRS one). That Add-on is something I definitely still intend to use now and then (I know about the drawbacks, but it makes sense for me in some particular cases).

tl;dr I can check a card in the card browser, it says (wrongly) that the retrievability is e.g. 80%, but when I open card info, it will be like 60%.

1 Like

It’s this issue:

Not sure if it was fixed after that. @L.M.Sherlock ?

probably the same issue as described here. if so, the fix is already made

Might be the same, as I’ve heavily used “Set Due Date” when going through Backlog. What I noticed was that intervals were very broken - e.g. I’d see a card with the interval 24 days, but 3 months after having actually seen it, and when I know it, the new interval is 1.5 months, which makes absolutely no sense (as it should be like 4.5-6 months).

I don’t think it’s related to that, the differences can be huge and definitely not due to rounding.

[Earlier discussion on Reddit - The heart of the internet ]


If you’re talking about an add-on that pushes all of your due dates by a certain number of days – aside from any of the general drawbacks, some of those are known to not work very well. (I suppose it’s not too surprising that a short-sighted, ill-considered, and outdated add-on would also have design issues.) Since you’re now seeing this inconsistency on cards it has affected, that’s all the more reason to avoid using it.

Perhaps it’s a failure of my imagination, but I can’t think of any “particular cases” that wouldn’t be better handled in some other way – like a catch-up deck, FSRS Postpone, or even Set Due Date. And I don’t think any of those would create this R inconsistency you’re seeing.

1 Like

Yeah, that’s the one. I mean, I might be missing something, but my situation is as follows: I had a fairly long hiatus with an obscene backlog, and after coming back and going through it, my daily workload is… obscene as well. On 90+% of the days I manage it, but some days life just gets in the way and I want to skip the day.

Yes, I know all about the Anki logic and how my recall will suffer, but in practice this approach has worked perfectly for me over many years and I’m ready to pay for that tradeoff.

Using FSRS Postpone, from what I gathered, will just increase my workload in the following days. What I usually do is postpone all cards due in the next 30 days by one day. That way, all cards that are 31+ days due will still be due on the same day, and the ones in the 30 days after the day I postpone them will be due a day later.

Is there a more reasonable way to handle that? And no, I am not adding any new material right now, but it will take a month or two more for the daily workload to be a bit more normal, and even then I won’t be able to make all my reviews a 100% of the time.

And, either way, my problem still persists. :smiley: Also, most of the time the intervals make sense, like, the one on my Card Info actually seems realistic, but I’d really like for a way to take the current interval into account when evaluating card’s memory state because this discrepancy is killing me.