Keep getting error “invalid params provided”

Anki Help
1

I am getting an “invalid params provided” error just about daily. Each time the only way that seems to “fix” it is to clear the FSRS parameters and then click “optimize current preset”. This causes the problem to go away for the rest of the day but it pops up again soon the next day.

I have tried clearing the FSRS parameters and leaving them cleared, tried clicking “optimize all presets”, tried “reschedule cards on change”, and tried “Check database” but nothing has helped for more than a few days.

I’m primarily using AnkiDroid but I see this on the Windows desktop version as well. Any help or tips would be much appreciated!

2

You’re using a much older version of Anki on Windows (23.10) than you are on Android. Each of those installs will use the parameters that are appropriate for its FSRS version, but clearing the parameters and optimizing on one won’t clear the parameters and optimize on the other.

The error you’re getting is rare, but it can happen for users with version mismatches like this. You’re on the right track to clear it up, but I suspect the problem is persisting because

  1. Not all of your presets are getting cleared, and they don’t all need new parameters when you re-optimize.
  2. You’re clearing and re-optimizing on one device, but not the other.
3

I have been keeping my ankidroid up to day but you’re right, my windows version is older. I just installed the latest version on Windows and will try harder to keep it updated.

I’m not sure how to address point 1, but if it happens again I will try to re-optimize on both devices.

Thanks!

4

You should be able to automatically check for program updates. In the preferences screen in the “Appearance” tab, there is a toggle for “Check for program updates”. I never used that feature (and don’t use windows) but would imagine that you’ll be getting a notification once a more recent anki version is available.

5

It has been nearly a week and I haven’t had the issue reoccur which is a big improvement. Looks like the different versions between Android & Windows was the issue. Thank you so much for the help!

1 Like
6

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