Troubleshooting Data Source Integrations

Why Isn’t My Data Pipeline Sync-ing?

Sometimes you might find that your data source pipeline doesn’t appear to be syncing data – that’s not great! There are a few reasons why this might be happening – this guide will walk you through actions you can do and common problems that might be affecting your pipelines, to fix that right away.

Initial Setup Authentication Errors

When you connect a data source with Blendo, you will need to provide the necessary credentials for Blendo to sync the data from that data source into your data warehouse. In case of wrong initial credentials, we will try our best to give you a descriptive message so you know where the problem is.

Other Authentication Data Source Errors

If you have succeeded to authorize Blendo, but you receive a notification that “your pipeline from {your source} to {your destination} database has failed at {time of pipeline execution} due to an authentication error…” it means that Blendo’s permissions to that service are no longer valid.

Reasons for this happening are:

• The credentials you used originally to authorize Blendo changed or are not valid anymore. For example, a username or password changed, an API key was invalidated. This could be the case for your data source (e.g Zendesk) or your destination (e.g your PostgreSQL database).
• The data source you are trying to connect has a downtime.
• Blendo is experiencing an internal issue.

Before contacting support here are workarounds you may try.

Verify your Credentials

Please verify you used the correct credentials with your data source. Things to check are:

• Username / Passwords

• API keys

• URL pages

• Permissions Settings

Some integrations may require certain user roles or permissions to access data.

In all of the above cases, please check the instructions of how to connect with your data source.

Data Source has Downtime.

Please check a comprehensive list with third-party status pages with those that support such information.

Re-authorize Data Source Integrations

If you need to reauthorize a data source integration please follow the next steps:

• Go to Blendo Dashboard
• Find the data source you need to reauthorize and click on it.

• Scroll down to the Settings section and click Setup.

• Depending on the authorization requirements of each data source you may need to Disconnect …

then re-authenticate or add your credentials from scratch.

 

and finally, click Validate and Save.

Data Pipelines doesn’t Move Existing (Historical) Data

The first time you connect a data pipeline Blendo will start pulling your data source data and push it into your destination database. Please make sure you understand how back the first pull can go as this is depicted in your configuration page. Here are some options you may see:

• In some data sources, we pull all the historical data (e.g Zendesk)

• Others ask for a time frame (e.g Mailchimp or Facebook Ads)

Can’t Connect a Second (Alternate) Data Source Account to Blendo

There are a lot of cases where users have 2 or more different accounts with a particular data source (e.g. multiple Facebook Ads accounts, multiple Shopify or MailChimp accounts). In Blendo, you can connect as many accounts as you want (within your tier limits). That being said, we sometimes get these questions:

• Why can’t I connect the 2nd account for my data source?
• Why does it always add my original data source account when I try to add another account?

Usually, what happens here is that you currently have an open session with your data source, i.e. you’re currently logged in to the account. Therefore, Blendo uses that logged in session when adding a new account.

To add multiple accounts follow the steps below:

• Add a new data source by clicking Add Source.
• If you are directed directly to the original data source account, click Disconnect. Note: This will not disconnect the previously added Data source.
• Proceed as normal with the authentication instructions of your data source.
• Viola! The new data source should be added now. Don’t forget to rename the data source connection hovering on the name and using the pencil icon to help identify the new connection.

If you still have issues please use the incognito mode of your browser as below.

• Open an incognito window in your browser.

• Login to Blendo using that incognito window.
• Add a new data source by clicking Add Source.

Since you’re in the incognito mode, there would be no open sessions/cookies for the said app data source. This should force the popup login to appear for that app.

• The new data source should be added now. Don’t forget to rename the data source connection hovering on the name and using the pencil icon to help identify the new connection.

Rate Limiting

Some services have API limits and throttling mechanisms of their own. As Blendo we need to conform to those rate limits but at the same time, we want to deliver your data. Example of such services is Salesforce or Freshdesk or Facebook Ads.

Blendo will always try to recover intelligently from that situation, so it will retry multiple times in the next sync schedules. If the problem remains and your pipeline is not pulling data then either you need to increase your limits (if possible) or contact our support for more help.

Internal Errors

Any service could face an internal error from time to time. As Blendo we need to inform you in such cases and at the same time, we want to deliver your data. An example of such a case could be a bug on the API side of a data source, that breaks the pipeline and will not allow it to continue.

You may also have a look on the Status pages of that integration. Blendo will always try to recover intelligently from that situation, so it will retry multiple times in the next sync schedules. Although we make our best to troubleshoot the issue, if the problem remains and your pipeline is not pulling data, then your best bet is to contact your app provided with more relevant information on the issue.

Service Unavailable Errors

It may be a case that we cannot connect to the data source service. As Blendo we need to inform you in such cases and at the same time, we want to deliver your data. An example of such a case could be a service experiencing downtime.

Blendo will always try to recover intelligently from that situation, so it will retry multiple times in the next sync schedules. In such cases, it is always a good idea to start from our third-party Services’ Status pages for that integration.

Blendo Status

Whenever Blendo encounters an issue or instability we will let you know with a notification.

Blendo will always try to recover intelligently from that situation and continue its process. We recommend that you reach our support team in case you have any questions.