Understanding data source refresh failures and error codes

This article contains answers to the following questions:

About data source refresh intervals

Klipfolio attempts multiple times to connect to a data source before disabling it. The recheck interval is designed to ensure that the maximum amount of time is given to retrieving any new data and to allow any errors to be cleared.

Refresh attempts use the following intervals:  

  1. After one failure, Klipfolio attempts to refresh again every 5 minutes until success.
  2. After three failures, Klipfolio attempts to refresh again every 30 minutes until success.
  3. After five failures, Klipfolio attempts to refresh again every 6 hours until success.
  4. After 20 failures, the data source is disabled.

If a data source is disabled, you can consult the Error Log to help diagnose the problem.

To view and edit refresh information and to find the Error Log for a data source:

  1. Click Data Sources in the left navigation bar.
  2. Select the relevant data source file.
  3. Under General > Connection, click View Refresh Info. The Refresh Information and the Error Log display.
  4. If you want to manually put the data source into the queue for refresh, click Queue for Refresh.
  5. If you want to change the refresh interval, under Refresh Information, click Edit and select an alternate refresh interval from the drop-down beside Queue for Refresh.
  6. Under Error Log, you'll find lots of helpful information. See the following section on analyzing the Error Log.

Analyzing the Error Log

The following information about a data source is available in the Error Log:

  • The last Refresh Date/Time
  • The length of time (Duration) to refresh the data
  • The current size of the data source
  • The result of refreshing the data source. (Click the link to check for any generated error message.)
  • The kind of data source
  • Whether the refresh was successful or not (Updated?)

Note: Data in the Error Log is purged weekly and is current for the last ten minutes.

Status Codes

Use the following error codes to help troubleshoot data source connection issues:

400: Bad Request The resource can no longer be found.
403: Forbidden Logon credentials are incorrect.
500: Internal Error The query request failed to resolve.

Troubleshooting data sources that fail to refresh

  1. Some APIs, like Google Analytics, impose a limit on the number of requests per profile, number of concurrent requests per profile, and the number of tokens per Google user account. For more information on the Google Analytics API, see Limits and Quotas on API requests.
  2. Some OAuth tokens expire and must be re-authorized on a regular basis. For example, a Facebook OAuth token must be re-authorized every two months.
  3. Some APIs impose a limit to the size of file you can upload. For example, most Box users are restricted to a maximum file size of 250 MB.
  4. Some data sources, such as SQL data sources inside your firewall, might require you to white-list our Klipfolio dashboard IP addresses. For more information on our IP addresses, see Whitelist IP Addresses
  5. A query might be incorrect. For example, a Google Analytics query returns a "Connection Service" error if there is a line break at the end of a query.
  6. A file name might be incorrect. For example, if a file in Dropbox has been replaced with a file using a different file name.

Related articles: