[Intel Map] History inconsistency, sometimes missing

in Report a Bug
Intel data sends sometimes data without history data while its expected.
This leads to incorrect highlights for visited/captured/scout controlled
I get in most cases data such as
// getEntities response: .result.map["16_15940_11535_0_8_100"].gameEntities[...] [ "90b381c9b22a487e8d780626f55741f5.16", 1614009101125, [ "p", "E", 44804023, -687323, 5, 85, 8, "http://lh3.googleusercontent.com/GAkS1tBPFwP-uM8hXx656peqZ8OEyoWm_fvH3MusUZzTcM8ThOo_Tm1UQ9LDmBZP1QbFl8OFvtvLKTevHJLJB-qP9Q", "For\\u00eat du Bourgailh - parcours v\\u00e9lo", [], false, false, null, 1614009101125, null, null, null, null, 3 ] ],
but sometimes, history is missing
// getEntities response: .result.map["16_15940_11535_0_8_100"].gameEntities[...] [ "90b381c9b22a487e8d780626f55741f5.16", 1614009101125, [ "p", "E", 44804023, -687323, 5, 85, 8, "http://lh3.googleusercontent.com/GAkS1tBPFwP-uM8hXx656peqZ8OEyoWm_fvH3MusUZzTcM8ThOo_Tm1UQ9LDmBZP1QbFl8OFvtvLKTevHJLJB-qP9Q", "For\\u00eat du Bourgailh - parcours v\\u00e9lo", [], false, false, null, 1614009101125 ] ],
6
Comments
I think it's worth pinging @ofer2 here for fast and competent response. Could you take a look please?
I'm experiencing this when panning standard Intel map sometimes. It shows portals, for example, as uncaptured, and then if I refresh the page it highlights them correctly. This might be the underlying problem.
Although our API is free to change at any time, currently, as an optimization, if there is no portal history, we simply dont send the list of nulls. ("No portal history" means that it didnt find it, I'm not certain if this can happen due to timeout, but I dont think so)
This is on the same portal though, so it's not that no history exists. The second call didn't return the history that we know can't be reversed by player actions.
Oh sorry, I didnt see that the data was on the same portal guid. My main thoughts are either timeout, rate limit, or memcache error....I'll try and take a look and see if I can figure out where this might be happening in the morning.
Sorry about the delay, I got sidetracked on other work yesterday and didnt have time to look into this. I think I've found the source of this issue and should be fixed shortly.
Thanks for the update!