davipt wrote:I have a user here in Portugal that reported the same. He logged in and had 0 points and no permissions to edit anything (and surely was on world.waze.com), but after some hours everything was back ok for him.
Please document areas lost here: viewtopic.php?f=10&t=31184
In my user's case I don't think it was related to that topic (*), as it was just a temporary glitch where all points and editing areas disappeared.
I've posted this because it may be relevant to the new WME, as I think it might be a case of resilience in case of backend timeout.
For example, when the backend is quite slow and timesout, the XHR call to /Descartes-live/app/Features may return an error but the old WME would say nothing - the "loading roads" would go away but then stuff would be missed, roads, landmarks, depending on the cache and how many timeouts. I don't know about the areas as I'm CM and don't have that layer enabled anymore).
On the new WME I'm seeing something similar happening, and it could be the issue from my friend. I'm seeing a lot the session going away and the new WME tells me nothing (unless I save). I just notice it because when I scroll the map the data is not updated, and notice even more because the highlights script stops highlighting the streets - as there was no response from that XHR call.
So my feeling, to keep this completely ontopic, is that the user was logged in, lost the session, scrolled around, tried to edit stuff and nothing was available. I don't think he tried to logout and login again though. And this is relevant because I've seen myself the case where the map doesn't update, I click refresh and get the login page, then click refresh and am logged in again.
Is the cookie session load balanced and maybe one node is returning an error?
(*) thanks for that link, let me just quickly note that in my case I see the drives becoming unavailable either after one month, or when a mapdate happens, and as the mapdates have been once per month, I can't relate to one case or the other