Connection issues Private preview

This guide helps you resolve common issues when setting up the Alteryx connector in Atlan.

Unexpected workflow input-output mapping in technical lineage

When you are setting up lineage for Alteryx workflows in Atlan, especially during private preview, you may encounter errors related to unexpected input-output mapping. These errors typically surface when Atlan doesn’t receive enough information from Alteryx to generate accurate technical lineage.

Error messages

Unexpected Workflow Input-Output Mapping in Technical Lineage

Cause

Atlan currently receives limited metadata from Alteryx as part of the private preview integration. This incomplete data results in an inability to correctly determine how input datasets relate to output datasets within workflows. As a result, the generated lineage may be partial, incorrect, or missing entirely.

How to fix

While this limitation is inherent to the current private preview, here are some steps you can take:

1. Verify all workflow inputs and outputs are explicitly defined with clear and consistent names.
2. Avoid using tools like Dynamic Input, Download, or Run Command that make data paths harder to trace.
3. Use consistent naming conventions for datasets and tools across all workflows.
4. Reorganize complex workflows into simpler sections to make lineage easier to infer.
5. Re-ingest the workflow in Atlan after making changes to check if the technical lineage appears correctly.
6. Contact Atlan support if the issue continues.