Time Zone Inconsistencies

I have noticed that all the Memrise Pro statistics (overall streak, daily learning events, and the performance monitor) turn over at midnight, GMT. My timezone it set for PST, and all of my course clocks turn over at midnight on my time, as they should.

However, I lost my overall streak recently because I didn’t have any learning events between 5:00 PM one evening, and 5:00 PM the next.

Furthermore, all of my learning events for today were counted as occurring on Monday, although even in Greenwich Mean Time they should have counted as Tuesday. This would appear to be a separate issue, but I suspect the two are related.

1 Like

At the moment, the Learning Streak Graph runs only on GMT.

Well, that’s interesting.

Be that as it may, there is still a bug.
According to my learning graph, Tuesday just started five minutes ago, and it is currently 12:05 AM, Wednesday, GMT.

Yes, the “learning graph” continues to be largely useless unless one can spend time learning every 12 hours. I broke a 28-day learning graph streak in US CDT (GMT-5) on 8/3 because I didn’t get around to starting my drills until after 11PM. What seems ridiculous to me is the learning graph shows 0 learning events on 8/3 while an individual course that I worked on from 11PM-midnight (CDT) on 8/3 shows a 31-day streak. Really strange design to use different algorithms to determine which day an event occurred on.

1 Like

Since this appears to be a continuing problem, I just set my time zone to UTC – basically, the modern name for GMT – as a workaround. :persevere:

You can change your time zone (region) on your profile (on the web site, anyway; not sure about the apps). When changing your time zone, Memrise cautions that you should complete all of your daily goals before making the change.

I’m hoping that this reply will call attention to the ongoing problem, without creating a topic that would basically be a duplicate.

Just calling this one up again. Any news Memrise on when it might get fixed? Having your learning streak graph on GMT only is definitely a bug fro the users perspective - even if its an intentional one from yours!

two years, and the devs still not fixing that issue…