"Random" new card order does absolutely nothing — same cards first every single time, no matter what I try (v3 scheduler)

I’ve spent an entire afternoon trying to get new cards to actually shuffle, and nothing works. Posting the full list of things I’ve tried in case it saves someone else the trouble, and because at this point I’m fairly confident this is a bug, not user error.

Setup:

  • Parent deck “German” with 4 subdecks: Other, Sentences, Noun, Verb (~11,000 cards total, imported via HyperTTS-generated audio)
  • Single shared preset (“Default”) used by all decks
  • v3 scheduler

Settings confirmed correct (checked repeatedly, on the parent deck AND on each individual subdeck):

  • New card gather order: Random cards
  • New card sort order: Order gathered
  • Insertion order: tried both Sequential and Random (yes, I ignored the yellow warning telling me not to touch this on v3)

The problem: The exact same handful of cards show up first, every time, in every subdeck, regardless of what I change. Examples: “blau”, “bzw.”, “pittoresk”, “spät” in the “Other” subdeck; “Orangensaft”, “Chemie”, “Idee”, “Jacke” in “Noun”.

Everything I’ve tried, in order, with zero effect on the outcome:

  1. Set “New card gather order” to Random cards (confirmed saved, confirmed applied to the correct preset used by all 6 decks)
  2. Set “Insertion order” to Random as well (against the UI’s own recommendation for v3)
  3. Full reset of all cards (Reset Card → “Reset repetition and lapse counts” checked) to force them back to New
  4. Manual Reposition on deck:German is:new with both “Randomize order” AND “Shift position of existing cards” checked — confirmed via Card Info that Position values actually changed (e.g. one card went from Position 56 → 1656 after reposition)
  5. Tools → Check Database (full rebuild of internal queues)
  6. Fully closing and reopening Anki (not just restarting the study screen)
  7. Studying directly from the subdeck (e.g. German::Other) instead of the parent deck, to rule out parent-deck subdeck-traversal order as the cause
  8. Syncing before closing, to rule out a stale AnkiWeb copy overwriting local changes on reopen

None of the above changed which card appears first. The same cards keep appearing first across multiple hours, multiple full app restarts, and multiple explicit re-randomizations of the position field in the database.

My working theory: the “random” gather for new cards seems to use a seed that’s deterministic per day (or per some other cached value that isn’t invalidated by Check Database, position changes, or app restart), so within the same calendar day you get the exact same “random” order no matter what you do. If that’s correct, it would be nice if this were documented somewhere, because right now the deck options UI actively suggests things (like “adjust the gather order instead” of insertion order) that have no observable effect.

Has anyone found an actual fix, or can a dev confirm whether this is expected behavior tied to a daily seed? Searching the forum I found several other people reporting what looks like the same symptom (e.g. “V3 Scheduler random not working”, “Anki unable to pick up new cards at RANDOM order”), so this doesn’t seem to be an isolated case.

Anki version: [26.05] OS: [Windows]

Off topic but interesting choice. FYI, if you are learning german and don’t specifically need this word, you could drop it. As a german, I don’t think I have seen or heard “pittoresk” being used, ever.

I’ll just post the links here as a service for others that may want to read those:

Are those cards New, and never been studied before? Or are they already introduced cards in Learn? For example, if you look at the screenshot in this comment – Anki unable to pickup up new cards at RANDOM order - #20 by azaz44 – that user is going to see hundreds of Learn/Relearn cards before they see any New cards. Learn/Relearn cards are in order based on when they reached the end of their step delay, so once they are available to study, their order is set.


If they are actually New, see this dev comment –