Error List

You may encounter a variety of errors when you interact with the Paradime platform. This section focuses on errors that can happen when you interact with the Paradime app.

PARA-1000: Missing production warehouse connection

This error happens you try to run a production dbt job in Bolt but don't have a production warehouse connection setup in Account Settings > Connections.

If you are referencing a target in your production runs that does not exist, then you will also get this error.

Solution

• add a production warehouse connection in Account Settings > Connections and make sure it's active and working

PARA-1001: Tableau Sign-in Error

The personal access token you used to connect to Tableau is no longer valid or has expired. This means that Tableau data assets will no longer be updated in the Lineage and Catalog. You will still have the data we have extracted when the integration was last seen working.

This can happen in a couple of scenarios:

• The person who connected the Tableau integration - their account is no longer active.

• The token itself had a defined validity and is now expired

Solution

• Visit the Integrations page

• Disconnect and re-connect the integration

• Enter the new / valid credentials during reconnecting

PARA-1003: Could not read from remote repository on Github

We could not fetch your dbt repo from Github and as a result the dbt run failed. This happens when the Github API is down or overloaded or is unresponsive.

Most times this goes away in the next run and is an intermittent issue with the Github API. However, we recommend you check https://www.githubstatus.com/ if there are any ongoing incidents with the Github API.

Solution

• Check the Github status page at https://www.githubstatus.com/ to see if there are any ongoing incidents with the Github API. If there are ongoing incidents, then this error will keep happening.
• Assuming this is intermittent, then trigger the schedule job manually if you don't want to wait for until when the schedule runs again.

PARA-1004: Lightdash CLI unavailable

Your current tier does not support running third-party CLI like Lightdash in the terminal or in your dbt™ production runs. Upgrade to the Growing or Scaling tier to get access to the Lightdash CLI.

You can easily upgrade from the Account Settings > Plans page.

PARA-1005: Elementary Data CLI unavailable

Your current tier does not support running third-party CLI like Elementary Data (edr) in the terminal or in your dbt™ production runs. Upgrade to the Growing or Scaling tier to get access to the Elementary Data CLI.

You can easily upgrade from the Account Settings > Plans page.

PARA-1006: "dbt docs generate" unavailable

In Paradime, you always have access to dbt™ model docs in the Data Catalog that is continously updated as you merge new code into your default branch. As a result, we don't support the "dbt docs generate" command.

PARA-1007: Couldn't fetch info-schema from Snowflake for production catalog

We could not fetch the information schema for your production data catalog. This could be for a few reasons as follows:

• The user in the Production Connection does not exist
• The user credentials in the Production Connection are invalid
• The user account in the Production Connection doesn't exist anymore in Snowflake
• The Snowflake account is expired

Solution

Please check the connection details in the Production Connection. If you are not sure if the credentials are correct, try testing again. If they don't work, talk to your Snowflake data admin to make sure you have the correct credentials.

Check our Production Connection details.

PARA-1007: Couldn't fetch info-schema from Snowflake for dev catalog

We could not fetch the information schema for your development data catalog. This could be for a few reasons as follows:

• The user in the dev warehouse connection does not exist
• The user credentials in the dev warehouse connection are invalid
• The user account in the dev warehouse connection doesn't exist anymore in Snowflake
• The Snowflake account is expired

Solution

Please check the connection details in the development warehouse connection. If you are not sure if the credentials are correct, try testing again. If they don't work, talk to your Snowflake data admin to make sure you have the correct credentials.

Check our dev warehouse connection details.

PARA-1008: Couldn't connect to git repository

We could not connect to the dbt™ git repository connected to your workspace. This can happen for a variety of reasons:

• The repository no longer exists

• The SSH key, used to connect between Paradime and the git provider, has been deleted in your repo

• The user account used to add the SSH key in the git provider, does not exist anymore

Solution

Please check that the repo exists and there is a working SSH connection between the Paradime workspace and your git provider.

As a last resort, follow the instructions on updating the git repository connection to reset the git connection.

PARA-1009: Couldn't connect to Hightouch

We could not connect to the Hightouch API. This can happen for a few reasons:

• The Hightouch API is down and our retries failed

• The credentials used for the Hightouch API are not valid

Solution

Disconnect and connect the integration following the Hightouch integration guide.

PARA-1010: Couldn't connect to Looker API or LookML repo

We could not connect to the Looker API. This can happen for a few reasons:

• The Looker API is down and our retries failed

• The credentials used for the Looker API connection are no longer valid

• The SSH connection between the LookML repo and your git provider is broken

Solution

Disconnect and connect the integration following the Looker integration guide.

PARA-1011: Couldn't connect to Fivetran

We could not connect to the Fivetran API. This can happen for a few reasons:

• The Fivetran API is down and our retries failed

• The credentials used for the Fivetran API are no longer valid. Fivetran allows only one API key and secret, so if someone changes that in Fivetran, the Paradime integration with Fivetran will start failing.

Solution

Update the credentials in the integration following the Fivetran integration guide.

PARA-1012: Couldn't fetch Tableau data

We could not fetch data from the Tableau API. This can happen for a few reasons:

• Tableau periodically runs backfill of its own metadata store from where we fetch the results over API. When the backfill is running, we don't get any response from the API. Depending on the size of your Tableau resource, this backfill could run for 1-2 days. During this time the data extraction can fail.
• The credentials used for the Tableau API are no longer valid

Solution

Disconnect and connect the integration following the Tableau integration guide. If it's a backfill problem, then disconnecting and connecting will not solve. So in case, the problem persists, reach out to support and we can help you out.

PARA-1013: Couldn't generate Lineage Diff report

We could not generate a the Lineage Diff report when opening a Pull Request. This can happen when Bolt is not yet configured. We require at least one active Bolt schedule in Paradime.

Solution

Configure your first Production schedule in Paradime following the Paradime schedule configuration guide. In case, the problem persists, reach out to support and we can help you out.

PARA-1014: Could't list Databases when running paradime sources generate

We could not list databases to generate dbt™️ sources.yml. This can happen when your development connection access level do not allow paradime to query information schema for your data warehouse.

Solution

Check our related docs based on your connected data warehouse provider here.

PARA-1015: Clear Paradime local storage

We sometimes encounter issues where the Paradime cache in the local storage needs to be cleaned. The following steps explain how you can do that in Chrome:

• Select the 🔒 icon next to the browser url and click on Cookies and site data

  

  Choose cookies and site data

• Click on Manage on-device site data

  

  Manage the on-device site data

• In the section, Data from the site that you're visiting, click on the 🗑️icon against the following domains:

  • api.paradime.io

  • app.paradime.io

  • paradime.io

  

  Clean the local storage

That's it, the browser local storage for Paradime will be empty now.