Custom Study V3 Bug

Anki 2.1.49 (dc80804a) Python 3.8.6 Qt 5.14.2 PyQt 5.14.2
Platform: Windows 10
Flags: frz=True ao=False sv=3
Add-ons, last update check: 2022-05-10 15:24:02

Caught exception:
Traceback (most recent call last):
  File "aqt\taskman.py", line 101, in _on_closures_pending
  File "aqt\taskman.py", line 71, in <lambda>
  File "aqt\taskman.py", line 90, in wrapped_done
  File "aqt\operations\__init__.py", line 112, in wrapped_done
  File "aqt\deckbrowser.py", line 123, in <lambda>
  File "aqt\main.py", line 1126, in onOverview
  File "aqt\main.py", line 672, in moveToState
  File "aqt\main.py", line 691, in _overviewState
  File "aqt\overview.py", line 60, in show
  File "aqt\overview.py", line 65, in refresh
  File "aqt\overview.py", line 184, in _renderPage
  File "anki\scheduler\v3.py", line 114, in _is_finished
  File "anki\scheduler\v3.py", line 49, in get_queued_cards
  File "anki\_backend\generated.py", line 44, in get_queued_cards
  File "anki\_backend\__init__.py", line 131, in _run_command
anki.errors.InvalidInput: Invalid input: <U+2068>bug: card modified without updating queue<U+2069>

I’m running no addons and I’m on Anki 2.1.49. I was just reviewing a custom study when this happened, and I haven’t done any other actions but pressing spacebar and 1/2/3. It is very similar to this report: “V3 bug. Card modified without updating queue” (from the user avmo), and I’ve also gotten this error from that page before:

Caught exception:
Traceback (most recent call last):
  File "aqt\webview.py", line 538, in handler
  File "aqt\reviewer.py", line 495, in _onAnswerButton
  File "aqt\reviewer.py", line 425, in _answerCard
  File "anki\scheduler\v3.py", line 160, in answerCard
AttributeError: 'NoneType' object has no attribute 'id'

I get the error when I click the custom study deck again, and it’ll be fixed by checking my database, however, Anki will say there are no more cards due for review.

Please follow the steps on When problems occur - Frequently Asked Questions

I’ve followed them to the best of my extents.

Did you confirm the issue still occurs with 2.1.51?