Thanks, Bad. I did forget about those other instances of unexplained but temporarily dropped blue bar. I’ll look back - I should be able to find those.
I have a working hypothesis related to how we store events. Each record in our event table represents a single annotation. Over time, we accumulated so many event records it was bogging down our system everytime we had to search to see if a user had already seen a movie. So Ieva came up with the idea to create an “events_history” table and move old events to that table. That way, we could still have access to the information but query only the most recent events for the purpose of selecting a new movie.
In examining the recent data, I noticed that there are overlapping ID numbers for the records in the event and events_history table such that when we join the two, depending on how the information is retrieved, it is conceivable that we would pull the wrong record. I don’t have solid evidence of this yet because I need to find the relevant queries in the code and then run them separately to see how they behave (which is what I’m doing now). In the meantime, I thought i would show you this:
Your user_id is 691. as you can see, for the same record id, there are two records, one is your recent answer to a calibration video, and the older one is a random annotation from 2018 that just happens to have the same row id. Again, my working hypothesis is that these two records are somehow getting conflated. But for some reason, only for you and MikeC, and only recently.
The record with ID 2197226 is the one where it all started. The system thinks you got that one wrong, but the status=5 means you didn’t, yet your FPR changed right after that.
So can you (or anyone) see anything in this table that would explain what is so special about the two records with ID=2197226?
(I’ve been looking at the same for MikeC and there is no pattern apparent to me)
In any case, I am hoping that testing out these queries on those particular records will shed light on the issue.