Troubleshooting

For information about logs, refer to Troubleshooting.

Refer to the following scenarios for which you might need to troubleshoot:

Multiple Dataflows Appear in Lineage

Problem

Multiple dataflows appear in the lineage chart.

Cause

  • When you create multiple datasources for the same Fivetran account.

  • If you’ve previously configured an Add-on Connector for Fivetran.

Solution

Ensure that you enable the compound layout dataflow.

Preflight Checks Fail: 403 Error

Problem

As a Catalog Admin, preflight checks fail with 403 error.

Solution

Enable the following permission flag to true:

alation.roles.allow_source_and_catalog_admins_to_create_ds true

Note

Contact Alation Support to enable flags if you’re on Alation Cloud Service.

Missing Cross-System Lineage

Problem

No cross system lineage generated after configuring Fivetran OCF connector on destination.

Solution

  • Verify if Fivetran connected sources and destinations are available in Fivetran and are cataloged in Alation.

  • Ensure that Additional Datasource connections is updated for all the Fivetran connected sources with the same host and port information provided while configuring source in Fivetran.

TMP Objects Appearing on Lineage Chart

Problem

If you see TMP objects for source in lineage chart.

Solution

Ensure that the respective metadata objects are already extracted and cataloged for source in Alation.

Connector Not Found During Lineage Extraction

Problem

If you get an error related to connector not found when you extract lineage.

Solution

Ensure you perform a Fivetran platform sync before running the lineage extraction in Alation.

../../../_images/FivetranResync.png

API Rate Limits Reached

Problem

API rate limits are exhausted

Solution

  • API rate limits can get exhausted and it depends on the available metadata for extraction.

  • HTTP 429 Too Many Requests: Connector goes in a sleep state until the next re-try based on Retry-After value fetched from Fivetran API response. For more information, refer to Rate Limiting in Fivetran documentation.

  • Verify the connector logs for alation.fivetran.util.HttpRestUtility - #################### Connector to sleep for :.

No ELT Sources in Wayfinder

Problem

You don’t see ELT Sources in Wayfinder.

Solution

Ensure that the following flags are set and have proper values:

  • alation.feature_flags.DEV_enable_otype_service is set to true.

  • alation_conf alation.feature_flags.DEV_otype_service_enabled_otypes has a value elt_source.

    • If not, copy and append the value:

      alation_conf alation.feature_flags.DEV_otype_service_enabled_otypes -s <append, elt_source to end of the output of above >

Note

Contact Alation Support to enable flags if you’re on Alation Cloud Service.