It could be related to this:
If so then the problem should go away soon. Fingers crossed!
2 Likes
I’ve just had a peek and seen that you signed up before the ominous 17.05.01 date - perhaps that has something to do with your not having problems (though I would have thought it would work the other way around…)
1 Like
The issue with the Heatmaps stemmed from that they were updating all recorded reviews with new info. If they are doing this for all reviews for every user then that is many millions of records. That could by why things are slow
2 Likes
I’m down to ~300! 
2 Likes
Ah, I see - I got the impression from the thread you’d linked that it should only be affecting historic reviews, but if they’re updating all recorded reviews with new info then that would indeed explain this bug.
It also seems like this hasn’t been applied universally all at once, which might also explain the jumping behaviour.
So perhaps the issue will indeed resolve itself in time.
1 Like
Yeah, what they explained in that thread was a bit different. They were saying they would update the assignments with a “passed_at” date. Doing that only requires at most checking every item once for every user. However, when I was looking into the issue with the heatmap script I found that they were updating all recorded reviews too, with different info. Judging by the dates on the updated reviews it looked like they hadn’t even gotten through 2018 yet. They might not be going by date, though.
4 Likes
We aren’t changing any data on review records. We are adding a new attribute to review. Thats about it. All other data remains unchanged, except updated_at, which gets touched when the record is updated. A official announcement will be made in a couple days what this new field is. But if you scour the API doc Github repo you can find information 
The assignment change is correct. But we aren’t changing all assignments. Just a small subset from pre-2017 which are in a specific state.
7 Likes
Got it 
I was being vague because the details aren’t really important in this context
From a beginner user perspective, I got confused what it wanted from me when it asked for “読み方”, since I haven’t learned that vocabulary yet. Perhaps better to keep it English like WK does, unless lower level users are not a target audience?
2 Likes
This looks interesting
1 Like
I’m afraid I don’t think the original developer is still active, so this isn’t likely to change.
Also, welcome to WaniKani! 
6 Likes
Yeah np. Just wanted to get the info out there.
2 Likes
Thank you!
I didn’t notice the thread was this old, since it had new replies. And it’s not that critical anyway, just confusing the first time.
2 Likes
It always asks for meaning and reading in the same order too, so once you’ve worked it out you’re set 
The thread is still active, just not the developer 
5 Likes
Speaking of info, can you answer some questions I had in the SRS systems update thread? I haven’t seen any updates on it in the GitHub repository, or I wouldn’t have bothered you. Sorry to do this!
Edit (17th June): If I had known yesterday there would be an announcement, I wouldn’t have posted this. I wish there was a place to find out that kind of thing…
I believe the annoucement planned on the 2020-06-17T07:00:00Z will answer some of your questions.
5 Likes
tentatively, it seems to be working again…? touches all the wood within reach
2 Likes
I just tried out BBB, but after answering eight questions, it started to repeat all the same questions again, even though I answered them perfectly. Is there any way to get it to stop asking you questions once you get them right?
It cycles through each item twice, as explained in OP.
2 Likes
Not sure if the OP is still around, but why was this done? Is there a way to change it?