Unable to split roads with HN's

Is this a…:
Standard bug
Steps to reproduce this issue:
Find any segment with HN’s, cut it and press save. You will get an Oops! Someone else has changed one or more map objects error.

I discovered this last weekend when trying to divide a road. It took me a bit to figure out the error and the message does not tell you what is wrong. In the attached you can see the street does not go through. In order to make this work you nor have to remove all the house numbers, save the segment, split and adjust the segment, add all the HN’s back.

Very tedious work for something that used to be simple.

Environment where the bug occurs…:
NA
Permalink:

Browser name and version:
Chrome
Are you using scripts? Please detail which ones.:
Tested incognito with the same error.


Not sure if I am missing a step, but when I split a segment with house numbers in incognito, it saves with no error.

Ok, I think I figured out the missing step. Or at least what got the error for me.

If I cut a segment and save, it works.
If I cut a segment, pull them apart, then save, I get the error.

So cutting, not separating, and saving works. Did you separate after?

I’ve been encountering this issue as well, the work around is right after you disconnect, connect, or re-connect a segment for your split hit save, then proceed. I share your frustration on the aggravation on doing like 30 edits deep and then having to start all over again.

1 Like

I just tested and you are correct, if you save right a way you can then move forward. I still need to test doing a divide,

Hello all,

I would just like to provide a quick update: a fix for this bug is currently in the release pipeline. We’ll keep you updated on the rollout.

Best regards,
Olesya

2 Likes

Hello all,

Following up on my previous update: the fix for this bug has now been deployed to production. Could you please verify on your end?

Thank you,
Olesya

I can confirm this is now allowing you to split, make other changes and then save.

1 Like

Excellent, thank you for the verification @AquaZR1.