Card modified without updating queue

I get a similar error:

Error
An error occurred. Please use Tools > Check Database to see if that fixes the problem.
If problems persist, please report the problem on our support site. Please copy and paste the information below into your report.
Anki 2.1.55 (01caec2a) Python 3.9.15 Qt 6.3.2 PyQt 6.3.1
Platform: macOS-13.1-arm64-arm-64bit
Flags: frz=True ao=False sv=3
Add-ons, last update check: 2023-01-05 10:12:50

Caught exception:
Traceback (most recent call last):
  File "aqt.taskman", line 122, in _on_closures_pending
  File "aqt.taskman", line 71, in <lambda>
  File "aqt.taskman", line 90, in wrapped_done
  File "aqt.operations", line 125, in wrapped_done
  File "aqt.reviewer", line 447, in after_answer
  File "aqt.reviewer", line 464, in _after_answering
  File "aqt.reviewer", line 229, in nextCard
  File "aqt.reviewer", line 260, in _get_next_v3_card
  File "anki.scheduler.v3", line 52, in get_queued_cards
  File "anki._backend_generated", line 47, in get_queued_cards
  File "anki._backend", line 148, in _run_command
anki.errors.InvalidInput: bug: card modified without updating queue

I get this sort on error each day now (early on in my daily reviews), maybe since upgrading to the v3 scheduler or maybe since upgrading to Anki 2.1.55, I can’t remember sorry.

That’s a different bug to the other reporter, and appears to be an issue with the v3 scheduler. It won’t cause any damage, but I’d like to get to the bottom of it. If you figure out steps to reliably trigger it, please let me know.

I haven’t figured out the steps yet.
It seems to happen only once a day, and early on in my daily reviews.
Here are screenshots from my phone from the error today:



Perhaps it relates to the day rollover? If the very first thing you do at the start of a day is to tap on a different deck to the previously selected one (and then the original after that if you wish), which will trigger a queue rebuild, does the error still pop up?

Today I tried (on my computer) starting the day by clicking on a different deck, doing a few reviews, then going back to my “All” (container) deck and doing my daily reviews as normal. Sadly the error still popped up:

Error
An error occurred. Please use Tools > Check Database to see if that fixes the problem.
If problems persist, please report the problem on our support site. Please copy and paste the information below into your report.
Anki 2.1.56 (07fd88dd) Python 3.9.15 Qt 6.3.2 PyQt 6.3.1
Platform: macOS-13.1-arm64-arm-64bit
Flags: frz=True ao=False sv=3
Add-ons, last update check: 2023-01-11 23:02:52

Caught exception:
Traceback (most recent call last):
  File "aqt.taskman", line 122, in _on_closures_pending
  File "aqt.taskman", line 71, in <lambda>
  File "aqt.taskman", line 90, in wrapped_done
  File "aqt.operations", line 125, in wrapped_done
  File "aqt.reviewer", line 447, in after_answer
  File "aqt.reviewer", line 464, in _after_answering
  File "aqt.reviewer", line 229, in nextCard
  File "aqt.reviewer", line 260, in _get_next_v3_card
  File "anki.scheduler.v3", line 52, in get_queued_cards
  File "anki._backend_generated", line 47, in get_queued_cards
  File "anki._backend", line 151, in _run_command
anki.errors.InvalidInput: bug: card modified without updating queue

Each day the error seems to happen at the same place, around the middle of my reviews of the first sub-deck.

I seem to have to sync before I can continue the reviews, otherwise the error keeps popping up.

I took a copy of your collection yesterday, and today ran a script to run through all the outstanding reviews answering first Again, and then Good, and couldn’t seem to trigger the issue. Are you performing other actions during the review, such as editing cards, suspending/burying any, etc?

I’ll need to tweak the error message to give us more context, so we can get to the bottom of this.

Please try again with the latest beta, which will print the card id when the error occurs:

https://betas.ankiweb.net/

If you could then look up the card via cid:<the id> in the browse screen and check its review history, and include a screenshot of the error, that may help to narrow things down. Please also run the following in the debug console to get the time it occurs:

from anki.utils import int_time; pp(int_time())

https://docs.ankiweb.net/misc.html#debug-console

I apologise for my slowness in replying. I have just installed the beta and will follow those steps when the error comes up again. Thank you.

The error just happened again.
Here is the screenshot of the error:

Here is the error report:

Error
An error occurred. Please use Tools > Check Database to see if that fixes the problem.
If problems persist, please report the problem on our support site. Please copy and paste the information below into your report.
Anki 2.1.57 (5cdfa7a6) Python 3.9.15 Qt 6.3.2 PyQt 6.3.1
Platform: macOS-13.1-arm64-arm-64bit
Flags: frz=True ao=False sv=3
Add-ons, last update check: 2023-01-26 10:17:11

Caught exception:
Traceback (most recent call last):
File “aqt.taskman”, line 122, in _on_closures_pending
File “aqt.taskman”, line 71, in
File “aqt.taskman”, line 90, in wrapped_done
File “aqt.operations”, line 125, in wrapped_done
File “aqt.reviewer”, line 446, in after_answer
File “aqt.reviewer”, line 463, in _after_answering
File “aqt.reviewer”, line 229, in nextCard
File “aqt.reviewer”, line 260, in _get_next_v3_card
File “anki.scheduler.v3”, line 52, in get_queued_cards
File “anki._backend_generated”, line 47, in get_queued_cards
File “anki._backend”, line 156, in _run_command
anki.errors.InvalidInput: bug: card modified without updating queue: id:1483179252769 card:1674789389 entry:1674687627

I looked up the card with the error printout id via cid in the browse screen:



Notice that this note is different to the error note (it’s Romans 4:19–25; the error note was Romans 4:16–18). The error card is:


Review history of the browser card:

Review history of the error card:

Here is the debug console:

Thanks Nick, that was helpful. If my suspicions are correct, turning on burying of new cards in your deck options should stop this problem from happening until we can get a proper fix out.