Will I EVER find the little stinker thats doing this?

AnkiDroid (Android) Help
1

Screenshot_20240821-080410
Screenshot_20240821-0804102160Ă—1058 162 KB

2

Due numbers depend on all of your collection I think. You can reposition all of your cards to fix that.

3

Screenshot_20240821-082706
Screenshot_20240821-0827062160Ă—1350 204 KB

There should be something from a different deck between the low due date number and the high one.
You sure this’ll work?

4

I think a long time ago I was also told to do a Check > Check database from the kebab menu. In any case, this isn’t necessarily a problem.

5

Check Database didn’t work here.
And when I tried to reposition everything, even when using “is:new”…

Screenshot_20240821-083119
Screenshot_20240821-0831192160Ă—1350 91.3 KB

And it also pops up sometimes saying it’s not responding. Looks like there are way too many cards to mass-reposition just like that.

6

Search is:new -is:suspended, see if it works now.

7

Screenshot_20240821-084718
Screenshot_20240821-0847182160Ă—459 71.1 KB

As you can see, it didn’t work.

8

Yes, Reposition is an edit action for each card, so using it on 32K+ cards would be quite taxing on the system.

Due numbers only matter relative to each other, so there isn’t an issue with having gaps in your New-queue.

If your goal here is to adjust your “bottom of queue” number so your new cards don’t get these absurdly high numbers [I’m guessing, because you still really haven’t said what help you’re looking for], you first need to use Reposition, but only on these very high numbered cards. Search for prop:pos>1000000 -is:suspended – is that a more reasonably sized set of cards?

You should reposition them to available New-queue numbers (because there’s no need to move any other cards for this, and AnkiDroid will always shift other cards on Reposition). From your screenshots, starting at 68600 looks like it would be clear, but I can’t tell if any of those are your full queue/collection.

Then after you reposition the cards, you can run Tools > Check Database to adjust the bottom of queue number.

For the future, this can happen whenever you import a shared deck that has high New #s, so keep an eye out for that.

9

Screenshot_20240821-113720
Screenshot_20240821-1137202160Ă—1350 26.3 KB

For some reason, there’s nothing there.
Nothing being here means there’s nothing to reposition. Where is this coming from?
It’s like the card isn’t even there, but there’s gotta be something.
The lowest queue number out of all my decks right now is 386.

10

Maybe put the wrong number there. But it’s not even a problem so you shouldn’t worry about it IMHO.

11

Did you already reposition those cards? What about without the “-is:suspended”? Try the next highest set of queue numbers from your screenshots – prop:pos>68000. Or just look at your is:new results again, and sort by the Due column to see where your largest numbers are. If you’re satisfied with that, then Check Database is the last step.

12

I already repositioned the cards. So I got the highest one in queue and put it in instead,

Screenshot_20240821-220415
Screenshot_20240821-2204152160Ă—1350 23.9 KB

Nothing. Again.

13

Oh, wait, when I checked with a test card, the floor is at a reasonable number now! Maybe check database finally fixed it?
Even though… I already did it before?

14

Yes, Check Database adjusts the bottom of the queue to the largest queue number. That’s why you need to Reposition those cards first and then run Check Database.