Impossible to approve PURs if it has an invalid house number

@numbermaniac @TimAThing @ypcyc @Karlsosha @DarkestWays @locojd1 @whoaitspete

Hello all,

Could you please check on your end and let me know the current outcome of your attempts to save previously reported PURs? As far as I have observed those that still fail are RPP-related PURs - we continue to investigate the root cause of that.

In case it fails for you, I would appreciate you letting me know if the house number in your PUR was:

  • valid;
  • invalid > tried correcting it but it failed to save anyway.

This is just to make sure we keep these two use cases separately.

Thank you,
Olesya

I was able to save the previously reported PURs and WME place edits that were failing. Still no luck with RPPs, as you mention.

After trying to Approved a PUR for a location that had the wrong address today, This time i was able to change the address and was able to save it normally, So it looks like the issue with approving PURs for locations that had a wrong address, now is fix and we can properly fix them and save them. now in the RPP PURs the issue still happening as per the last time i got one which was yesterday.

Thank you @Olesya-Staff for following up on this. Unfortunately, my previous example RPP has since then disappeared. The other one reported by numbermaniac is now OOMA.

Though it does seem like RPP specific issue. I’ll have to find another example if I can.

Hi @Olesya-Staff
I was trying to approve PUR for RPP with incorrect character in House number that I have replaced so that HN would be valid, but WME gives me error

Can confirm that the one I reported at the start of this thread is still impossible to approve. Changing the house address from “26/1” to “26” still doesn’t let me save it.

1 Like

Thank you all for your feedback, I will report it back to the relevant team. If you see any new examples, please drop them in this thread so we can review them.

Have a great weekend!
Olesya

I’m facing issues too. I was helping a newbie with adding house numbers to an unnamed PR and because the house numbers are all unit numbers, it was impossible to add either style of house number.

This is the PR I am talking about. Each house on it has a unit number (e.g. 24/16 Sturt Lane). Because it is an unnamed PR, traditional HNs aren’t suitable, but we also can’t add RPPs because of the naming issue.

I hope this is fixed soon.

Thanks,
DFTP

Hello @DeviateFromThePlan,

Thank you for your example and your patience. I can imagine how frustrating it must be for you… But on a more optimistic note, I can assure you that the issue has been prioritized accordingly and we should have a fix deployed soon.

Kindest regards,
Olesya

2 Likes

Thanks @Olesya-Staff! I understand this isn’t the most important thing on your desk, but your help is greatly appreciated. :thumbsup:

Looking forward to that fix! :slight_smile:

1 Like

Just had another RPP with bad house number. With latest WME it is not approvable:

https://waze.com/en-US/editor?env=usa&lat=40.95753&lon=-75.98182&zoomLevel=20&venues=186122650.1861357568.20867819&venueUpdateRequest=186122650.1861357568.20867819

App Allows free from text as a house number. So the user did 54 n james st, Hazelton, PA 18021

Hello all,

Quick update: the fix has been deployed to all environments. Could you please check whether it has taken effect on your end?

Thank you,
Olesya

Hello @Karlsosha,

I cannot see the RPP you are referring to, just the HN. Has the RPP been rejected?

Best regards,
Olesya

Oops. I think I rejected them on Autopilot. Let me try creating a place with a bad address. It auto accepts when I do it.

1 Like

I still can’t approve the one I linked at the top of the thread. It gives me the same error message.

Hi @numbermaniac,

Thank you for your feedback. I have asked the team about this specific use case and will get back to you once I have received more information.

As always, thank you for your patience!

Best regards,
Olesya

Here is yet another PUR that cannot be approved - https://waze.com/en-US/editor?env=usa&lat=38.89601&lon=-76.94859&zoomLevel=19&venues=185532805.1855000370.20900639&venueUpdateRequest=185532805.1855000370.20900639 The house number “Papa John” is obviously invalid, but even if I change it to a number, I still can’t save the change.

Edit: It appears another editor must have rejected the PUR, so it is no longer available on the map. :frowning:

Steps to reproduce this issue:
Yes you can reproduce it. Whenever someone adds a place as a residential place. When I try to save it, it says that there is an invalid house number. I tried to remove it, but the same warning keeps coming. I also tried to change it to public and removing house number, but still persists.

WME Beta Permalink:
https://beta.waze.com/en-US/editor?env=row&lat=36.12884&lon=43.97268&zoomLevel=19&venues=28836201.288165405.39893433&venueUpdateRequest=28836201.288165405.39893433
This bug occurs in:
All environments
WME Beta version number:
v2.290-7-g43d9e8490
Are you using scripts? which ones?:
Road Selector, WME Toolbox, Junction Angle Info, WazeWrap, Route Speeds


Issue is not fixed yet
I got several PURs with name in HouseNumber
https://beta.waze.com/en-GB/editor?env=row&lat=56.96196&lon=22.41832&zoomLevel=18

1 Like

Yes, this bug was fixed in the past. As far as I can see today, it is back again🤦‍♂️

Another sample: https://waze.com/editor?env=row&lat=40.22972&lon=49.58318&s=1900032773119366660046&zoomLevel=20&venues=32506258.324931511.39957227