Error -17329: Types Conflict in TestStand

Issue Details

When working with TestStand sequence files and custom step types, you may encounter the following run-time error: 
Error Code: -17329; Invalid type - conflicts with an existing type.

Solution

1. Check Station Settings
   
   • Verify the Allow Automatic Type Conflict Resolution setting under Configure » Station Options » File.
   • Recommended setting:
     • Only if a Type Palette File will not be Modified (default).
     • This allows TestStand to automatically resolve harmless conflicts without prompting.
   • Other options:
     • Only if a Type Palette File has the Higher Version
     • Never
       • Note Changing these settings after saving updated types can increase conflicts.
       • 
2. Use the Type Conflict Dialog
   • If TestStand cannot resolve the conflict automatically, you will see the Type Conflict in File dialog. Options include:
     • Use Type from File – Load the type from the sequence file.
     • Use Type in Memory – Keep the type currently loaded.
     • Rename One of the Types – Safest option when changes are significant.
     • Cancel – Abort loading the file.
3. Maintain Type Versions
   • Increment type versions whenever making intentional changes.
   • Do not disable prompts for type changes—warnings help prevent accidental propagation.
   • Coordinate changes with your team if using shared type palette files.
4. Best Practices
   • Keep type palette files under source control.
   • Confirm changes before saving modified types.
   • Use the Modified flag as an indicator of edits.
   • Stick to default station settings for balanced automation and safety.

Additional Information

• TestStand uses type definitions with version fields and modified flags. A conflict occurs when:
• • Two versions of the same type exist in memory or files.
  • Versions differ or modified flags are set.
  • Automatic resolution settings prevent silent resolution.
• TestStand can resolve conflicts automatically if:
• • Type versions differ.
  • Neither type has the modified flag set.
• Default behavior:
• • Automatically resolves conflicts unless a type palette file would be modified.
  • Prompts only when there’s a risk of unwanted type propagation.