Thread got promoted on Latest Updates...
View attachment 4738329
Update date didn't change...
View attachment 4738324
I'm assuming this is a side effect of the cache cycles...
i see what happened. there is still this old bug i mentioned before, where after like a month of the cache api being online, the latest updates watcher just stops for no apparent reason, i noticed some things were showing up in latest updates but not detected within 5 mins, so i could tell this is what was wrong, checked the server and indeed it has stopped watching latest updates 10 days ago.
so what happened is: latest updates were not being watched, so it did not notice the new info when it was published, it noticed the new version with the 12-hourly version check, and so it detected the update. however, when it detected the new version, the update had not been promoted to latest updates yet, so it had the old date, and when it did get promoted it did not notice this because the updates watcher was broken.
im confident this shouldnt happen again: i made the cache api restart the python process every 24 hours, so the updates watcher will no longer manage to get stuck; also, ive made the latest updates watcher (the 5 minute one that should do the heavy lifting for detecting updates) check the first 4 pages of each category instead of only 1, so it should be able to detect most changes for the 360 most recent games on latest updates within 5 minutes always now. for those not in the first 360 by update date, there is ofcourse the usual 12-hour version check, and the 7-day max cache validity.