Katalyst: Export fails when experiment contains unsupported or custom data types

Description

• Some experiments contain:
  • Custom data types or metadata fields.
  • Experimental features from pilot integrations.
• Export to a downstream system fails, often with messages about unknown or unsupported fields.

Solution

• Identify unsupported elements:
  • Check export logs or error details for specific field names or data types causing failures.
• Export configuration:
  • Adjust mapping to:
    • Exclude unsupported fields from the export, or
    • Map them to generic fields where appropriate.
• Clean up experiment metadata:
  • Consider removing or simplifying custom fields for export, if they are not needed in the target system.
• For ongoing workflows:
  • Align custom data field design with the export schema; avoid adding fields that cannot be represented downstream, or handle them as optional annotations.