PUR shows non-existent location change

Is this a…:
Standard bug
Steps to reproduce this issue:
A number of PURs show a change in location when there isn’t one. If you hover over the “suggested” location widget, no suggested location is shown. (If you hover over the “current” location widget, the location is highlighted as expected, as seen in the screenshot.) If you accept the PUR, there is no record in the venue history of a location change.

The permalink attached to this report is one example, but I have seen several others in the past few days. Note: this particular PUR is invalid and can be rejected after investigation of this issue is complete.

Environment where the bug occurs…:
NA
Permalink:
https://waze.com/en-US/editor?env=usa&lat=38.89162&lon=-77.05096&zoomLevel=18&segments=83867491,57747486,9284817,69990343,77590605,535367144
Browser name and version:
Chrome 131.0.6778.205
Are you using scripts? Please detail which ones.:
Yes, but confirmed in incognito mode.

1 Like

FYI, your PL is for 6 segments not the place. I think the correct PL for the PUR is https://waze.com/en-US/editor?env=usa&lat=38.90834&lon=-77.01042&marker=true&zoomLevel=19&venues=185467269.1854607155.1686548

I did find where the “suggested” location is actually located at, which is probably related to a reported bug where PURs are getting sent to 0,0 lat/lon

Thanks, my mistake with the PL.

I can replicate this bug too. The suggested location is Lat: 0.00 Lon: 0.00.
The permalink attached is one testing example. I have seen a lot of location change in PURs these 1-2 weeks.
Environment where the bug occurs… :
ROW
Permalink :
https://waze.com/en-US/editor?env=row&lat=47.15078&lon=28.11319&zoomLevel=18
Browser name and version :
Brave Version 1.73.91 (Chromium: 131.0.6778.85 (Official Build) (64-bit))
Are you using scripts? Please detail which ones. :
Tested with / without script. Same issue.

Yes, hovering over the widget shows nothing but clicking on it will snap you over to null island.

Hi, we already have internal issue for this, I will let you know about updates.

2 Likes

Hi, this issue was fixed: there should not be any new PURs with invalid suggested location. Please note that we didn’t do anything with already existed invalid PURs - I suppose they all will be rejected. Please monitor and let me know if you see newly created invalid PURs.

2 Likes

New PUR with suggested location at 0,0, added within the past 24 hours: https://waze.com/en-US/editor?env=usa&lat=38.92924&lon=-77.02361&zoomLevel=18&venues=185467269.1854541621.3244455

1 Like

Thanks, I will double check.

Hi,
I can confirm that this issue is still happening for new PURs.
Cheers,
Eddy

Could you please share with us PLs of new PURs so we can surface it to the team?

Thanks in advance!

https://www.waze.com/en-US/editor?zoom=7&lon=-78.184891&lat=39.159803&venues=184680840.1846939468.815860&env=usa

https://www.waze.com/en-US/editor?env=usa&lon=-80.40507&lat=27.47640&zoomLevel=20&venues=183238931.1832323772.20029744&venueUpdateRequest=183238931.1832323772.20029744

PUR submitted Jan 28th. Editor who submitted the request confirmed they didn’t move the PP, only submitted an alternate name, but the PUR included a suggested location of 0,0.

3 Likes

Thanks, I passed this example to the internal issue.

3 Likes

PUR dated Jan 23 exhibiting the same issue. Confirmed without scripts. PUR appears to be submitted in-app (can you determine this on the back-end?). I’ve seen a few of these over the last week but haven’t recorded them until now.

https://waze.com/en-US/editor?env=usa&lat=42.85970&lon=-85.71175&zoomLevel=19&venueUpdateRequest=179765677.1797591230.607890

1 Like

It was still doing it to me this morning, even in an incognito window (so no scripts running).
image
Shows the location I was taken to when I asked wme to take me to the new suggested location.

Hello all,

Just a quick update: the fix has already arrived in Prod.
Should you observe any invalid suggested locations, please let us know.

Best regards,
Olesya

1 Like