Skip to main content

Error message summary

If it detects an error due to merging, it will display an error message in the Git console. Resolve the error by referring to Example of error handling during merging.

Error message composition

The error message is configured and displayed as follows.

  • Error code
  • Error summary
  • Error details

Example error message

[ERROR: e1001] Model "Interrupt XXX" is conflicted.
File: UseCaseModel-A.nmdl
Id: XXXX
"Description" field: Own is "XX.", Other is "YY.".
"Unit" field: Own is "cm/s", Other is "m/s".

Error message details

Shows the configuration details of the error message.

1. Error code

The following is displayed at the beginning of the error message. See Error Codes Table: Error Code Columns for error codes.

[ERROR: error code]

2. Error summary

The following message will be displayed according to the target.

No.CategoryTargetContentError CodesError Messages
1FileSchema VersionFile Schema Version Collisione0001File versions are different.
2Editing conflictsModelField value changes collide with each othere1001Model "{model name}" is conflicted.
3Deleting a model and changing the field value of that model conflictse1002Model "{model name}" is conflicted by deleting and editing.
4Deleting the parent model and changing the field value of the child model conflictse1002Model "{model name}" is conflicted by deleting and editing. Note 1
5RelationshipField value changes collide with each othere2001Relation of "{related model name}" is conflicted. Note 2
6Deletion of related or related source/destination model and change of related field value conflicte2002Relation of "{related source model name}" is conflicted by deleting and editing. Note 2
7Deletion of related or related source/destination parent model and change of related field value conflicte2002Relation of "{related source model name}" is conflicted by deleting and editing. Note 2 , Note 3
8Interaction modelInteraction element changes collidee3000Interaction Model "{model name}" is conflicted.
9Product line modelFeature model changes conflicte4001Feature Model "{feature name}" is conflicted.
10Feature assignment conflictse4002Feature Condition Formula of "{model name}" conflicted.
11Config change conflictse4003Configration "{product name}" is conflicted.
12Constraint conflict between featurese4004Constraint of "{the name of the feature to which the constraint is related}" is conflicted.
13ProfileProfile changes conflicte5000Profile is conflicted.
14ProjectProject changes conflicte6001Project is conflicted.
15Trace setting information conflictse6002Trace Setting "{trace setting name}" is conflicted.
16Trace Excluded Setting is conflicted.E6003Trace Excluded Setting is conflicted.
17Error due to model inconsistencyModel, associationOwning association becomes a circular referencee9001"{Related reference source model name}" contains circular reference.
18Multiple ownerse9002"{model name}" has multiple owners.
  • Note 1: The error code and message are the same as No.3.
  • Note 2: A similar message is displayed in the case of a related conflict with a related.
  • Note 3: The error code and message are the same as No.6.

3. Error details

The following is indented and displayed after the message.

  • file name
    • Shows the file name that contains the conflicting target element.

      File: UseCaseModel-A.nmdl

  • Model ID
    • Displays the ID of the target element whose name is displayed in the error message.

      Example Id: XXXX

  • Field conflict information
    • Lists information about conflicting fields.

      Example "{field name}" field: Own is {changes in the current branch (own)}, Other is {changes in the specified other branch}.