# Statistics Messed Up After FSRS Reschedule

**URL:** <https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622>\
**Category:** Help\
**Created:** [January 20, 2025, 5:30pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622 "2025-01-20T17:30:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 20, 2025, 5:30pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/1 "2025-01-20T17:30:13Z")

</div>

Hey y’all,

I recently “rescheduled my FSRS cards on change.” It went fine - I’ve read the discussions on this thread about the backlog. However, when I did it, it really messed up my review stats. To be clear - I didn’t actually review all these cards on the massive spike day - the backlog was actually minimal. Is there anyway to fix this?

TLDR: rescheduling my cards on change caused my review graph to spike to a level that did not actually happen.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/anki2/original/3X/1/2/12126a79f13de71030574980d76fe1496c691220.jpeg)

---

<div class="post-metadata">

**Author:** ![Expertium](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/expertium/32/24176_2.png) [@Expertium](https://forums.ankiweb.net/u/Expertium)\
**Post date:** [January 20, 2025, 5:41pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/2 "2025-01-20T17:41:06Z")

</div>

I believe you have already posted on r/Anki and @L.M.Sherlock said he will take a look at your collection

---

<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:** [January 20, 2025, 5:43pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/3 "2025-01-20T17:43:34Z")

</div>

Looks like the same issue as [Thousands of unexpected reviews logged all of a sudden](https://forums.ankiweb.net/t/thousands-of-unexpected-reviews-logged-all-of-a-sudden/53310)

This is caused by a mismatch in the Anki versions on different devices.

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 20, 2025, 7:01pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/4 "2025-01-20T19:01:12Z")

</div>

Yeah LM told me to post here

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 20, 2025, 7:06pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/5 "2025-01-20T19:06:05Z")

</div>

Is there a way to fix it without going into the SQL database?

---

<div class="post-metadata">

**Author:** ![Danika\_Dakika](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/danika_dakika/32/17815_2.png) [@Danika\_Dakika](https://forums.ankiweb.net/u/Danika_Dakika)\
**Post date:** [January 21, 2025, 1:45am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/6 "2025-01-21T01:45:00Z")

</div>

Since it’s just stats (I know, I know, stats are important, but they aren’t _going_ anywhere!), hold off on messing with the database until the dev finishes looking at it. From this and other reports (including the one vaibhav linked, and [on Reddit](https://www.reddit.com/r/Anki/comments/1i565m3/statistics_messed_up_after_fsrs_reschedule/)) – it looks like Reschedule revlogs are being miscategorized or being counted where they shouldn’t be. Since there were some changes around this in the last release, I think it should be fixable!

---

<div class="post-metadata">

**Author:** ![L.M.Sherlock](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/l.m.sherlock/32/16770_2.png) [@L.M.Sherlock](https://forums.ankiweb.net/u/L.M.Sherlock)\
**Post date:** [January 21, 2025, 4:11am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/7 "2025-01-21T04:11:39Z")

</div>

I think `check database` should fix this problem. If not, we need implement it.

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 21, 2025, 4:17am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/8 "2025-01-21T04:17:56Z")

</div>

Thanks, appreciate your help guys. I used the check database function but it didn’t fix it.

I’ll stay tuned before going into SQL, I don’t wanna mess it up lol

---

<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:** [January 21, 2025, 4:44am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/9 "2025-01-21T04:44:21Z")

</div>

Edit:  
Using Check Database on Anki 25.02 or later will fix the issue.  
If multiple devices are affected, use check database on all of them after ensuring that Anki is up-to-date. One-way sync won’t be required.

* * *

My suggestion before release of Anki 25.02:

Try all the steps I mentioned in that thread. To summarise,

- update all your devices to the latest Anki version (Anki and AnkiMobile 24.11 and AnkiDroid 2.20)
- check if the issue is gone (unless permanent damage has occured, the issue should go away just after updating)
- check if any of your devices shows the correct stats. If yes, do a one-way sync from that device.
- as a last resort, edit the database

Also, an advice for future readers, DON’T use check database while trying to fix this issue. I think that if you use check database on Anki \< 24.11, the temporary issue will become permanent. In more technical terms, check database on Anki \< 24.11 will think “this type = 5 is an invalid entry, let’s convert this to type = 0.”

If you have to edit the database to correct the issue, the following command in the debug console should work. Please make a backup before using it.

```py
mw.col.db.execute("update revlog set type=5 where type=0 and time=0 and ease=0")

```

~~Note: This command can create problems if your database contains actual learning revlog entries with time = 0. This can happen if you used some add-on for grading cards. In that case, you will have to limit the query based on the ids of the revlogs.~~ (not valid after the command was updated based on feedback)

After running this, ensure that everything looks alright and then do a one-way sync from Desktop to Ankiweb.

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 21, 2025, 4:59am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/10 "2025-01-21T04:59:01Z")

</div>

> [@vaibhav](#):
>
> ```auto
> mw.col.db.execute("update revlog set type=5 where type=0 and time = 0")
> 
> ```

Thank you so much!! The debug in the console worked perfectly.

For those that are not code minded like me: to open the debug console, click “ctrl shift + :” paste the code and then click ctrl enter.

---

<div class="post-metadata">

**Author:** ![mausprz](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@mausprz](https://forums.ankiweb.net/u/mausprz)\
**Post date:** [January 21, 2025, 6:26pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/11 "2025-01-21T18:26:06Z")

</div>

> [@vaibhav](#):
>
> If you have to edit the database to correct the issue, the following command in the debug console should work. Please make a backup before using it.
> 
> ```auto
> mw.col.db.execute("update revlog set type=5 where type=0 and time = 0")
> 
> ```

I’d like to suggest an alternative _safer_ command (based on my observations in the previously mentioned [post above](https://forums.ankiweb.net/t/thousands-of-unexpected-reviews-logged-all-of-a-sudden/53310/5) that all mismatch reviews also have and `ease` set to 0):

```auto
mw.col.db.execute("update revlog set type=5 where type=0 and time=0 and ease=0")

```

⠀

Although I would like to know what others think.

---

<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:** [January 21, 2025, 6:38pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/12 "2025-01-21T18:38:27Z")

</div>

> [@mausprz](#):
>
> ```auto
> mw.col.db.execute("update revlog set type=5 where type=0 and time=0 and ease=0")
> 
> ```

Yeah, this is safer and would work fine.

I edited my comment to include this command so that the future readers will first encounter this one.

---

<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:** [January 24, 2025, 8:08am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/13 "2025-01-24T08:08:16Z")

</div>

I don’t think it’s connected to check DB. I think it’s just caused by syncing the revlog entries to an older client that doesn’t understand them. I’ll update the DB check in the next build to handle it.

---

<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:** [January 24, 2025, 8:23am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/14 "2025-01-24T08:23:14Z")

</div>

By the way, I am curious how do users end up having this problem on all of their devices? Revlogs can’t be modified by a normal sync. So, even if the type is modified on an older client, how does the revlog type on the other (newer) client get altered?

---

<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:** [January 24, 2025, 11:43am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/15 "2025-01-24T11:43:00Z")

</div>

A one-way sync would be my guess.

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 25, 2025, 3:33pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/16 "2025-01-25T15:33:08Z")

</div>

Hey guys - just want to highlight this for when you do the patch in the next update. The code fixed my desktop, but my mobile devices are still showing the wrong stats. Even after check DB.

---

<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:** [January 25, 2025, 3:58pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/17 "2025-01-25T15:58:34Z")

</div>

> [@vaibhav](#):
>
> After running this, ensure that everything looks alright and then do a one-way sync from Desktop to Ankiweb.

As I said earlier, you need a one-way sync from Desktop to correct the revlogs on other devices.

Go to Preferences → Syncing → On next sync, force changes in one direction.

---

<div class="post-metadata">

**Author:** ![jakegand](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jakegand](https://forums.ankiweb.net/u/jakegand)\
**Post date:** [January 25, 2025, 4:25pm UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/18 "2025-01-25T16:25:33Z")

</div>

Yep that worked thank you!! Sorry, I misunderstood what a one way sync was.

---

<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:** [February 12, 2025, 6:30am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/19 "2025-02-12T06:30:37Z")

</div>

An update:  
Using `Check Database` on Anki 25.02 or later will fix the issue.  
If multiple devices are affected, use check database on all of them after ensuring that Anki is up-to-date. One-way sync won’t be required.

I have also edited the post marked as the solution to mention this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex002/uploads/anki2/original/1X/8f1279ababc5879d54e4838989f606cfe55af8c7.jpeg) [@system](https://forums.ankiweb.net/u/system)\
**Post date:** [March 14, 2025, 6:31am UTC](https://forums.ankiweb.net/t/statistics-messed-up-after-fsrs-reschedule/54622/20 "2025-03-14T06:31:17Z")

</div>

Closed on March 14, 2025, 6:31am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.