Unable to connect segment

Cant seem to connect this segment (nor save it with the “None” checkbox selected for name)

https://waze.com/en-US/editor?env=usa&lat=40.48062&lon=-86.10788&s=412387220757&zoomLevel=21&segments=531834016

I’ve tried:

  • Chrome
  • Firefox
  • Prod
  • Prod without scripts
  • Beta without scripts

I can’t seem to cause either IN-931 or the Vaile segment to split at all. Confirmed another user in the US state menager chat was also not able to do it.

If I can get it to make the change at all, it hangs on save.

Update: I was finally able to connect the segment and save; however I still can’t make any changes to the segment geometry or turn instruction overrides and save them

I was able to change the geometry and save, although the screen did freeze on saving. Have you tried deleting and recreating it?
Seems to possibly be some corruption with that segment

The segment in question is a new segment. I actually did try disconnecting all the nodes in that intersection and saving but it gave me an error saying to reconnect the segments to the node

I just tried deleting the segment and recreating it. aside from all kinds of save errors, it worked, BUT I can’t get the turn restrictions to enable

Nothing is on a tile border, so there is some sort of corruption there, but it doesn’t appear to be a WME issue. It should be passed up the ladder to the SCM to look at.

1 Like

I could try deleting all the segments and recreating all of them from scratch? not a fun task but I’m not sure what else to do

That was going to be my next suggestion

From what I can tell that might be a fairly significant number of segments. Something seems to be up with this whole section of 931 and connecting roads.
Not that it’ll even let me do it though, can’t even seem to delete the segments

It could be a corrupt tile. I’d push this up to the SCM

How do I do that?

Answered in DM. But for the sake of others, take it to your a/rc

Thanks all,

I was able to reproduce this and have opened a bug to the WME BE team.

I’ll update once this is resolved.

Best,
Brett

Hi all,

I’ve heard back from the team, and they have found a workaround for this by disabling the paths layer.

The root of this issue is a conflict between the paths set up between segment 1 and segment 2, with segment 3 interfering with a different path with segment 4.

The team is continuing to take a deeper look into this issue, so if there are more updates I’ll post them here.

Thanks
Brett, on behalf of the Map Team

2 Likes

Hi @phoenixhawke,

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.