# Refresh counts on decks screen when learning card becomes due

**URL:** <https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122>\
**Category:** Suggestions\
**Created:** [September 30, 2024, 4:16pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122 "2024-09-30T16:16:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vaibhav](https://avatars.discourse-cdn.com/v4/letter/v/c68b51/32.png) [@vaibhav](https://forums.ankiweb.net/u/vaibhav)\
**Post date:** [September 30, 2024, 4:16pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/1 "2024-09-30T16:16:08Z")

</div>

When I am on the Decks page and a learning card becomes due, the count doesn’t increase. If, however, I click on the deck, the overview page shows the correct count.

This is not a problem if I have some other cards to review because I will open the reviewer anyway. However, if I have reviewed all of my other cards, it is possible that I may not even know that a card has become due.

---

<div class="post-metadata">

**Author:** ![sorata](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/sorata/32/34115_2.png) [@sorata](https://forums.ankiweb.net/u/sorata)\
**Post date:** [September 30, 2024, 4:41pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/2 "2024-09-30T16:41:33Z")

</div>

To add to it, this behaviour also causes other issues in the Android client where overview screen would show learning cards as buried cards.

---

<div class="post-metadata">

**Author:** ![dae](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/dae/32/65_2.png) [@dae](https://forums.ankiweb.net/u/dae)\
**Post date:** [October 2, 2024, 1:10pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/3 "2024-10-02T13:10:05Z")

</div>

IIRC, the page refreshes every 10 minutes.

---

<div class="post-metadata">

**Author:** ![vaibhav](https://avatars.discourse-cdn.com/v4/letter/v/c68b51/32.png) [@vaibhav](https://forums.ankiweb.net/u/vaibhav)\
**Post date:** [October 2, 2024, 2:21pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/4 "2024-10-02T14:21:35Z")

</div>

I didn’t realise that. Because I start creating new cards after completing my daily reviews, I always thought that I must have accidentally triggered the refresh of the page somehow.

But still, have you considered triggering a page refresh whenever a card becomes due rather than updating it periodically (push vs pull, basically)?

---

<div class="post-metadata">

**Author:** ![dae](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/dae/32/65_2.png) [@dae](https://forums.ankiweb.net/u/dae)\
**Post date:** [October 2, 2024, 5:05pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/5 "2024-10-02T17:05:11Z")

</div>

It could theoretically be done by noting when the next due card will appear, and refreshing then.

---

<div class="post-metadata">

**Author:** ![vaibhav](https://avatars.discourse-cdn.com/v4/letter/v/c68b51/32.png) [@vaibhav](https://forums.ankiweb.net/u/vaibhav)\
**Post date:** [October 2, 2024, 5:11pm UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/6 "2024-10-02T17:11:08Z")

</div>

Isn’t that more resource-efficient than the current method where the page is refreshed every 10 minutes?

Is there any drawback of the proposed method (apart from the need to invest some time for developing it)?

---

<div class="post-metadata">

**Author:** ![dae](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/dae/32/65_2.png) [@dae](https://forums.ankiweb.net/u/dae)\
**Post date:** [October 4, 2024, 8:21am UTC](https://forums.ankiweb.net/t/refresh-counts-on-decks-screen-when-learning-card-becomes-due/50122/7 "2024-10-04T08:21:28Z")

</div>

It’s just more complicated. It would be a little more efficient.
