The old PURs are no longer visible in the WME

[GabiruX]

Discrepancy PUR Count in WME Feed

Describe the problem*: Hello, I’m not sure if everyone is aware, but in Brazil we use a dashboard (https://wmebr.info/ur/purs_report.php?country=Brazil) to improve management. All countries can use it as well. Anyway, what I’d like to report is that in some Brazilian states’ dashboards, there’s a noticeable discrepancy between the number of PURs shown in the dashboard and in WME. For example, in Rio de Janeiro, WME currently shows 127 PURs, while the dashboard shows 780. After running a few tests to identify the cause, I found that several PURs are not appearing in the WME feed, even when using a fully open filter. These PURs only appear if I click directly on the place. I’m not sure if this is happening with other types of reports, but I’ll share this with the community. If anyone notices similar behavior with URs, MPs, or Map Suggestions, please report it below. Here are some examples of PURs older than 60 days that do not appear in the WME feed but do appear in the dashboard. Once again, they only show up if I click on the place. https://waze.com/pt-BR/editor?env=row&lat=-22.72330&lon=-43.24609&zoomLevel=15&venues=207619621.2075868528.2324572 https://waze.com/pt-BR/editor?env=row&lat=-22.70879&lon=-43.14643&zoomLevel=17&venues=207685157.2076982640.9523942 https://waze.com/pt-BR/editor?env=row&lat=-22.89235&lon=-43.27864&zoomLevel=19&venues=207554083.2075671903.40467846 https://waze.com/pt-BR/editor?env=row&lat=-22.77450&lon=-42.93141&zoomLevel=17&venues=207816228.2077965675.7966888 https://waze.com/pt-BR/editor?env=row&lat=-22.50477&lon=-43.18177&zoomLevel=18&venues=207619623.2076327302.1855057 What device were you using?: beta-in-car How are you connected to the car?: Cable Car Model: Samsung Car year: 1800 What is the bug affecting?: WME Can you reproduce it?: Always Happens Operating system*: beta-android Device Information*: Samsung Waze Version Number*: 5.11.5.1 How badly did this affect use of the product?: Medium [95459937-1118-45e4-bc80-e73566866f35.png] [f2660225-f76a-4343-98ac-104edd524aeb.png]

There is same bug here

For more infos…