[BUG] Set due date issues

ZornHadNoChoice · April 30, 2026, 4:00pm

Credits to the user on reddit for reporting this: Reddit - Please wait for verification

The following assumes that FSRS is enabled.

1 The exclamation hint is still shown

AnkiDroid hides the option to set the interval to the same value, as was mentioned in Set Due Date: Hide 'set interval to same value' if FSRS is enabled.

2 The intervals shown are wrong

Setting the due date with 99999, results in the interval being shown as 1.6 years in the browser and 68.1 years in the revlog.

3 The interval only changes the first time

If you set the due date to 1 then to 99999, it’ll still have an interval of 1.
This doesn’t happen on AnkiDroid.
Probably because of Set Due Date: Set interval to actual elapsed days when FSRS is enabled by L-M-Sherlock · Pull Request #4035 · ankitects/anki · GitHub.

4 The interval affects the scheduling

If you use set due date of 99999 on a new card, then rate it Good using the “Grade now” feature, or through filtered decks (or, I imagine, by waiting 99999 days), then the card will be scheduled to about a 100 years!

This doesn’t happen if you first review the card or use the “Grade now” feature. Also, using a shorter interval or the bug number 3, will give much more normal answer button intervals.

Debug info

Anki 25.09.2 (3890e12c) (ao)
Python 3.13.5 Qt 6.9.1 PyQt 6.9.1
Platform: Windows-10-10.0.19045-SP0

===Add-ons (active)===
(add-on provided name [Add-on folder, installed at, version, is config changed])
Advanced Copy Fields ['1898445115', 2024-01-08T20:01, 'v0.4.01', '']
AnkiConnect ['2055492159', 2025-11-09T22:40, 'None', mod]
AnkiWebView Inspector ['31746032', 2023-06-27T22:26, 'None', '']
Disconnected Review-Log Cleaner ['1067771610', 2025-06-10T16:28, 'None', '']
Local Audio Server for Yomichan ['1045800357', 2023-06-19T06:57, 'None', '']
The KING of Button Add-ons ['374005964', 2025-01-28T01:26, 'None', mod]

===IDs of active AnkiWeb add-ons===
1045800357 1067771610 1898445115 2055492159 31746032 374005964

===Add-ons (inactive)===
(add-on provided name [Add-on folder, installed at, version, is config changed])
No Distractions Full Screen Fixed by Shige ['1370336700', 2024-08-26T08:08, 'None', mod]

Also tested on AnkiDroid 2.24.0alpha14.

A_Blokee · May 7, 2026, 12:12am

This is tricky because it’s baked into the already translated string. Logged here:

github.com/ankitects/anki

"Set due date" description includes invalid "!" option while FSRS is enabled

opened 12:10AM - 07 May 26 UTC

Luc-Mcgrady

Ref: https://forums.ankiweb.net/t/bug-set-due-date-issues/69585 > *The following… assumes that FSRS is enabled.* > 1 The exclamation hint is still shown > > image > <img width="493" height="211" alt="Image" src="https://github.com/user-attachments/assets/40332996-0835-44d3-b751-a3408a34b97f" /> > > AnkiDroid hides the option to set the interval to the same value, as was mentioned in [Set Due Date: Hide 'set interval to same value' if FSRS is enabled](https://forums.ankiweb.net/t/set-due-date-hide-set-interval-to-same-value-if-fsrs-is-enabled/53890). https://github.com/ankitects/anki/blob/0e31efac08cddf0a43ad0b44f05f2a8e6ef0d91a/ftl/core/scheduling.ftl#L166-L169 This is hard baked into the string. Maybe just remove all "!"s from this string if FSRS is enabled to avoid re-translation work?

Fixed here:

github.com/ankitects/anki

fix: Use floats when displaying card intervals (#4788)

main ← Luc-Mcgrady:interval-display

opened 12:04AM - 07 May 26 UTC

Luc-Mcgrady

+15 -17

## Linked issue (required) fixes #4787 ## Summary / motivation (required…) While it is impossible during normal use to get an interval greater than 10 years due to the max_interval. By using set date you can get a larger interval which is then displayed incorrectly. By using a float to store the second values instead of a u32, we can display higher values (although the day interval is still constrained by u32). ## Steps to reproduce (required, use N/A if not applicable) 1. use set interval with a massive number 2. check the 3. ## How to test (required) Follow the steps to reproduce. The number will display as the actual interval in all instances. ### Checklist (minimum) - [X] I ran `./ninja check` or an equivalent relevant check locally. - [ ] I added or updated tests when the change is non-trivial or behavior changed. ### Details ## Before / after behavior (optional) <img width="1073" height="783" alt="image" src="https://github.com/user-attachments/assets/8c0b785a-9a0c-4deb-af2c-5c5d33879940" /> <img width="1073" height="783" alt="image" src="https://github.com/user-attachments/assets/58db3060-68d0-45bb-91d6-935d35d0ffa5" /> ## Risk / compatibility / migration (optional) Since the value is at max MAX_u32 * 82_000 maybe we should use a u64 instead? largely a moot point as accuracy doesn't matter for the time display functions. ## UI evidence (required for visual changes; otherwise N/A) ## Scope - [X] This PR is focused on one change (no unrelated edits).

I can’t reproduce this

Does this still fall under while having FSRS enabled because if this is with SM2 then I believe it’s intentional (Although I imagine rating it shouldn’t set it to 100 years because of the max interval). I can’t reproduce it with FSRS enabled.

(this is on the earlier mentioned fixed branch so maybe that helps?)

ZornHadNoChoice · May 7, 2026, 12:58am

Thank you!

Yes, as I mentioned at the top of the post.

Did you try bugs 3 and 4 on a new card each?

A_Blokee · May 7, 2026, 2:35pm

Nope I didn’t…

I can reproduce it now and have (hopefuly) fixed it:

github.com/ankitects/anki

fix: Use fsrs config bool for set due date (#4792)

main ← Luc-Mcgrady:use-fsrs-config-bool-for-set-due-date

opened 02:32PM - 07 May 26 UTC

Luc-Mcgrady

+12 -8

## Linked issue (required) fixes #4791 ## Summary / motivation (required…) Previously, using set due date on a new card was broken for FSRS because new cards didn't have a memory state which was how the set due date function determined if FSRS is enabled or not. See https://github.com/ankitects/anki/pull/4035#discussion_r2107488134. ## Steps to reproduce (required, use N/A if not applicable) 1. create a new card 2. set it's due date 3. set it's due date again 4. the due date won't change 5. use grade now 6. the card will be scheduled based on the future date due date rather than now ## How to test (required) I followed the reproduction steps and instead, after using set due date the interval is always set to 0; as to not affect grade now. ### Checklist (minimum) - [X] I ran `./ninja check` or an equivalent relevant check locally. - [ ] I added or updated tests when the change is non-trivial or behavior changed. ### Details ## Before / after behavior (optional) ## Risk / compatibility / migration (optional) ## UI evidence (required for visual changes; otherwise N/A) ## Scope - [X] This PR is focused on one change (no unrelated edits).

It was actually because of this so the link was a huge help:

Topic		Replies	Views
Intervals do not always match desired retention FSRS	9	204	June 25, 2025
"Set Due Date" changes Interval without "!" Scheduling	8	186	November 9, 2025
Bug: Bad reschedule behavior when "ignore reviews before certain date" is on FSRS	11	167	March 31, 2025
FSRS with known new cards FSRS	18	726	July 5, 2024
FSRS-5 increased interval by 5+ years FSRS	19	811	January 27, 2025

[BUG] Set due date issues

1 The exclamation hint is still shown

2 The intervals shown are wrong

3 The interval only changes the first time

4 The interval affects the scheduling

Debug info

Related topics