Duplicate External Providers from matching_feed

JasonN899 · February 9, 2026, 3:08pm

Is this a…:
Standard bug
Steps to reproduce this issue:
I am seeing places that have been edited recently by the Matching Feed account, that will goes around and updates/add the external provider link to places in WME, add the incorrect external provider link.

Blatantly incorrect, the link it added is over 400m way from the place point it was working on. The address of the link was incorrect and didn’t match the address of the place point it was working on.

I found about 3 or 4 of these in Ocean City Maryland. I fixed them before realizing the pattern. The picture attached is the one I have left alone so that you can investigate.

In the picture provided you can see the Blue highlighted place has the incorrect address, and is over 400m away from this place pin. Also, as a note, the 5301 address is in WME as a candy kitchen place point and is linked correctly. So this external link was now on 2 places simultaneously.

Environment where the bug occurs…:
NA
Permalink:
https://waze.com/en-US/editor?env=usa&lat=38.38715&lon=-75.06552&zoomLevel=19&venues=186712448.1867321087.1975837
Browser name and version:
Chrome

Olesya-Staff · February 10, 2026, 1:40pm

Hello all,

I’d just like to apologize for taking long to provide a meaningful update on this issue .
We are aware of the impact this is having on your editing flow and we’ve made sure it has been prioritized accordingly.
The issue is quite complex and therefore requires careful investigation to resolve.
I’ve asked the team for some more details and will update you once they are provided.

Thank you for your patience,
Olesya

JasonN899 · February 10, 2026, 1:43pm

@Olesya-Staff The bug i reported is not exactly the same as this thread. This thread adds duplicate (same name same address) external providers. This is not such a big deal as they may be in the same location.

In my example, it is adding totally incorrect addressed external providers that are hundreds of meters away and will cause significant routing issues.

Olesya-Staff · February 10, 2026, 1:54pm

We have this case recorded internally as well - both duplicate and incorrect matches have been reported.
I’ve asked the team if the task they are working on is supposed to address both issues. If not, I can split this bug into two. I’ll keep your report open until it’s confirmed.

Thank you,
Olesya