Message
Feature not associated with a run.
Severity
Crucial.
Detailed Description
All route features must be associated to their parent run objects. If the features are not associated to the run, then they will not be brought into the workspace by normal means. However, you always have the ability to bring them into the workspace using the Object Type property.
Possible Cause
In earlier versions (prior to Version 3.0), selecting a feature and changing the run could result in this error, especially when the run to which the feature is being moved is a read-only run. However, this problem has been identified in the route code and has been fixed. This error should not occur in Version 4.1 or beyond.
Possible Impacts
You are not able to modify the feature (assuming you had brought the feature into the workspace using Object Type filters).
Examples: Moving the feature or changing the type (short code) from GATE to BALL does not work.
What You Should Do
You must select an appropriate parent run.
Example: If the selected feature is a pipe feature, you should select the pipe run to which it should belong.