Route sequence changes when calculating in a RouteName after initially loading in stops.
Last Published: September 2, 2016ArcGIS for Desktop
Bug ID Number
June 30, 2015
September 24, 2021
ArcGIS for Desktop
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
As designed. The network analyst window listens to feature modified events for feature classes in network layers and maintains the sequence IDs within a group name. Sequence IDs start from 1, and are contiguious with no duplicates. As we calculate the field route name field on a per feature basis we listen to the feature modified event and assign a sequence value.
What is happening is that the logic that updates sequence values sees a new route name being created and so it assigns a new sequence value to it. The first row with a changed route name gets a sequence value of 1, the second 2, etc without regard to the pre existing stop sequence. The order in which features have their route name field calculated determines the order of the sequence ID created. In this case it happens that the first row with an updated route name and a newly created sequence of 1 is the last row which had a sequence of 4.