MTE Waze Events list : Issues

Is this a…:
Standard bug
Steps to reproduce this issue:
When I want to attach a closure to an event, I have a huge list that includes all past events, and it’s not easy to find the good one.

It should be filtered to match the closing date.

The same goes for the waze events page

Environment where the bug occurs…:
All environments
Permalink:

Browser name and version:
Chrome 137.0.7151.120
Are you using scripts? Please detail which ones.:
No

5 Likes

Wanted to enter same finding yesterday and postponed to today.
:wink:

Hi @asph4lt,

Thank you for submitting this bug report. Could you please record a video to show how you’re searching for the event? I tried to reproduce the issue on my side using the location from your permalink but didn’t see the same long list of events.

Many thanks in advance!
Nataliia

Hi @Nataliia_Staff ;

The size of the list doesn’t really matter it’s linked to the bug, what’s missing, and what’s important, is that the date doesn’t act as a filter, we should only see proposed events that fall on that date.

This is how things worked before the changes.

If I want to modify/duplicate an event, I don’t do it in this tab, I do it in the events tab.

Regards

edit: Another thing I’ve just noticed is that we can now add closures to a past event, before we couldn’t, there was an error that appeared.


Hi,
It seems that I get now a whole list of events in the drop down list when I want to link a closure to an event.
Possible events, including the locationless:


The dropdown I get:



etc, etc, etc.
That can’t be the intention, can it?
Cheers,
Eddy

1 Like

Hi Everyone,

Thank you for flagging this problem. I’ve filed an internal issue, and the team will work on it.

I’ll keep you posted on any updates we receive.

Regards,
Nataliia

4 Likes

Also happening to multiple editors in The Netherlands!

I should note this is adding significantly more work to placing RTCs and creating MTEs. Whether it be sifting through the giant list or differentiating between an expired MTE or the present one.
Many large scale events occur annually and differentiating between the active event for this year or the one from last year can only be done by trial and error.

1 Like

Screen Recording 2025-06-21 090200 (1)

1 Like

Hi Nathalia
isn’t this because of https://www.waze.com/discuss/t/filter-and-duplicate-events-and-closures-features-are-now-live/384357?

1 Like

Experiencing the same issue. Please revert to how MTEs were handled before. Usually the RTC list of MTE’s only populated current MTEs and only MTEs that were in the vicinity of where you’re editing/adding RTCs. I’m now seeing a whole super long list of all events in my state past and present. Whatever was changed is NOT useful and is, in fact, more time consuming to the workflow of adding RTCs tied to MTEs.

Hi Everyone,

I want to let you know that the team is actively working on this issue and treating it as a top priority. We’ll keep you updated on the progress.

Regards,
Nataliia

3 Likes

Hi Everyone,

The team has applied a fix for this issue. Could you please check on your side and confirm if the problem is resolved?

Thank you in advance!
Nataliia

1 Like

Hi,
It doesn’t seem that it’s working in my case. I still get a very extensive list of (non related) events.


Cheers,
Eddy

Hi @searchjaunt,

Could you please send the link to the location, where you you check events?

Thanks in advance!
Nataliia

Hi @Nataliia_Staff ,

At first glance, in the beta editor, it seems to be fixed, but in production the problem remains.

Thank you

Here it is: https://waze.com/editor?env=row&lat=51.40671&lon=4.76472&marker=true&zoomLevel=17&segments=88603107

The problem persists in this area too.

Hey @asph4lt,

You’re right — that was my mistake. The fix has been released to WME Beta only for now. I’ll update you once it reaches production.

Hi @searchjaunt,
Hi @ojlaw,

Could you please recheck the behaviour in the WME beta?

Just a heads-up — you might still see past events when creating closures. This happens because the backend includes all events linked to closures in the area, even if they’ve already ended. You may need them in order to duplicate past closures in the same area.

If you feel this behavior is confusing or could be improved, feel free to open a suggestion explaining how a change in the logic might be helpful.

Regards,
Nataliia