Troubleshooting connected table refresh errors

This topic refers to functionality that is not available to accounts on the Quick Base Essential plan. If the functionality described here does not match what you're seeing in Quick Base, your account is probably on this plan.

Sometimes, we may not be able to refresh your connected data. The connection owner can usually resolve this using the information below. If you’re still having trouble, please reach out to our Customer Care team.

Connecting to cloud services

If you're having trouble connecting or refreshing data from cloud services, you may see one of the following:

If the error includes... this means... Fix the issue by...

Column does not exist

Invalid field

Does not recognize queried object

The connected table is looking for a column in the service that no longer exists or is not accessible, based on permissions granted by the connection.

The column in the service may have been deleted.

Access privileges in the service may have been changed or the current connection may not have access to the table or fields.

If you don't need this field, remove the field from the connected table and edit the connection filter, if it includes any unavailable fields.

If you need access to this data, sign in to the service with the same credentials and find out if the data is accessible.

You may need to make adjustments to your account, or if the data is not accessible using the credentials you signed in with, you'll need to use a connection with different credentials. See switch connections.

Query requires additional inputs

Requires credentials

Login verification failed

Invalid credentials

The login to the data source isn’t working.

Verifying your credentials and/or access to the data source and then test and update your connection.


Table source not found

We’re having trouble accessing a table in the data source.

Try again later.

Creating a connection to

If you're having trouble creating your Salesforce connection, check with your administrator to make sure API access and permissions are enabled. requires that your account have API access enabled. Your user account must also have the API Enabled permission selected.

See Salesforce User Permissions for more information.

Connecting to a table in another Quick Base app

If you're having trouble connecting to or refreshing from a table in another Quick Base app, you may see one of the following:

If the error includes... this means... Fix the issue by...

No such operation

SSL connection required

Unknown hostname

Reading the QuickBase API_Authenticate response from ...
QBI_GetDBInfo failed

Reading the QuickBase QBIGetDBInfo response from ...
API_Authenticate failed

the Quick Base URL is incorrect

Locate the Quick Base URL in the browser. For example,

Copy and paste the correct URL into the Quick Base URL field.

Don’t include the /db/ portion and what comes after it when copying and pasting into the Quick Base URL field.

Be sure to use https instead of http in the Quick Base URL field.

No such database or login operation requires a database name

the database ID is missing or incorrect

Open the home page of the app.

In the URL that displays, copy the alpha-numeric text that displays after db/. For example, bi4zjv7mq.

Invalid application token

the application token is missing or incorrect

Copy or create an app token for the app you want to connect to.

On the app home page, click Settings, then click Manage Application Token. Copy and paste the app token into the App Token field.

Connecting to the Admin Console

If you are a realm admin and you do not see the Admin Console channel as an option listed in the sources when setting up a new connected table, check to make sure you have not exceeded the limit of 3 Admin Console connected tables per realm.

Connecting to a folder containing CSV files

If you're having trouble connecting to a folder containing CSV files, you may see one of the following:

If the error includes... this means... Fix the issue by...

Table replication requires non-null key values

There are empty cells in the column used as the Refresh Key field

Updating the CSV file to include a value for this field in each record or change the Refresh Key.

We couldn't open the fields list

  • The CSV file has empty fields in the header row or duplicate fields in the header row. Each field in the header row must have a unique name.
  • There are duplicate values in the Refresh Key field or a missing value in the Refresh Key field.
  • The file name ends in .csv, but the file is not UTF8-encoded

Updating the CSV file so that each field in the header row has a unique name.

Saving the file as a UTF8-encoded .csv.

Making sure the value in the Refresh Key field is unique for each record (no duplicate entries or missing entries).

The resource '[[connection_3226]]."Complete data export":ServiceDefinitionTable' does not exist.

The connected folder could not be found within the Quick Base Sync folder in the file storage service (Box, Dropbox, Google Drive)

Making sure the folder displays in the file storage service, inside the Quick Base Sync folder, and that it contains a valid .csv file.

The source data includes non-unique key values, the column value(s) from the source query that correspond to the destination key column(s) must be unique.

Multiple rows in the CSV file have the same value in the Refresh Key field

Reviewing the structure of your CSV file and the intended use of the data to determine how best to resolve duplicates and understand which column, containing unique values, makes the best Refresh Key for your data.

Unknown column: IndexName

An expected column name was not found in the CSV file

Review your CSV file to determine if a column name changed.

Error parsing .csv. A cell contains an invalid quoted string.

The CSV file does not conform to the standard, such as a value containing an un-escaped double quote

Review your CSV file and ensure that is it a UTF-8 encoded .csv files in which:

  • values are separated by commas
  • the same number of values are in each row
  • values containing special characters (commas, double quotes, and line breaks) must be enclosed in double quotes
  • if double quotes are used, then a double quote within a field must be escaped by preceding it with another double quote, for example "aaa", "b""bb","ccc"
  • leading and trailing blanks are not ignored
  • the first row contains the column names (no blanks or duplicates)

The file was example.csv. The error was: Invalid character in row 00001, field 1, position 1.

The CSV file contains a character that is not a valid UTF-8 character

Locate and remove the invalid character. The error message identifies the first invalid character that is encountered in the file. The file’s header row is considered row 1. The field (column) number is based on the order the connected fields were added to the connected table. The position is where in the field the invalid character is located.


Note: If your automatic refresh schedule was set to manual because of a number of unsuccessful refresh attempts, review the most recent error message in the table history and resolve the problem. After you resolve the problem, you can reset the refresh schedule to automatic.

If you’re having trouble, please open a support case.

View connected table details and history

To view Details about your connected table, including the connected service, connection owner, connected fields, filter, and schedule for the connected table, access the connection in Table Settings. You can also view a History of recent refreshes, and edit the connection filter, refresh schedule, or switch to use a different connection, if necessary.

View, test, or delete your connections

To view details about your connection and test, change, or delete connections, click the user dropdown on the Global bar, then click My preferences. Your connections display in the My Connections area.

Important: Deleting a connection for Gmail, Google Drive, or QuickBooks will invalidate other QuickBase Sync connections that were created with the same Gmail, Google Drive, or QuickBooks log in credentials. This happens because when a connection is deleted, we send a request to the connected service to revoke the OAuth token that was used by that connection. When Google or QuickBooks receives the request, they invalidate all the OAuth tokens for Quick Base Sync for that user. The connections in Quick Base will fail until the connection owner reauthorizes the connection to get a new valid OAuth token.

Related topics: