David
August 11, 2025, 4:02pm
1
Users don’t know how to resolve this error, and we don’t auto-fix it:
The FSRS context isn’t apparent to the user
impl From<FSRSError> for AnkiError {
fn from(err: FSRSError) -> Self {
match err {
FSRSError::NotEnoughData => AnkiError::FsrsInsufficientData,
FSRSError::OptimalNotFound => AnkiError::FsrsUnableToDetermineDesiredRetention,
FSRSError::Interrupted => AnkiError::Interrupted,
FSRSError::InvalidParameters => AnkiError::FsrsParamsInvalid,
FSRSError::InvalidInput => AnkiError::InvalidInput {
source: InvalidInputError {
message: "invalid params provided".to_string(),
source: None,
backtrace: None,
},
},
FSRSError::InvalidDeckSize => AnkiError::InvalidInput {
source: InvalidInputError {
message: "no cards to simulate".to_string(),
source: None,
backtrace: None,
},
Maybe using something similar to deck-config-invalid-parameters (if the error is similar):
The provided FSRS parameters are invalid. Leave them blank to use the default parameters.
1 Like
sorata
August 11, 2025, 5:24pm
2
I’m more curious about where these errors are coming from. I have seen them around here recently but upon testing, it seems Anki doesn’t even allow saving invalid params.
So I was under the assumption that it’s people with some old versions of Anki who are facing the issue.
dae
August 19, 2025, 7:01am
3
Logged on UX: Improve ‘invalid params provided’ error · Issue #4278 · ankitects/anki · GitHub
Agreed that we should fix the cause of the underlying issue, but I’m not sure what it is yet.