Waze pass suddenly broken, required a replacement to fix

We’ve recently discovered that one of the camera-enforced roads for which a pass was added in Waze no longer allowed anyone to drive through, no matter which passes they had set. As it turns out, this seems to have something to do with the pass having changed its name. After we updated the segment restriction to use the “new” name, it worked fine again. I think we were getting the ID of the pass in the past, instead of the user-friendly name.

Permalink of the two segments that use pass “BE: 9100 Priesteragiewijk Sint-Niklaas”

It might be interesting to look into how many other passes were affected by this (we couldn’t find any other examples within Belgium) as it’s not always immediately apparent to editors that this change has happened. In this case, we were able to identify it quickly because a nearby resident, who has the pass, alerted us of this. This happened a couple of days ago, but we needed to wait for the map update to validate that the change fixes the issue.

HI @Glodenox,

We apologize for taking a while responding to this issue.

Since this case doesn’t seem to be very common and is getting outdated, we will automatically close this bug now.

If this issue is still occurring please submit a new bug with all the relevant information and we’ll make sure to fully revisit it again.

We apologize for the inconvenience.

Thanks and have a great day.