Sometimes, Quickbase 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, reach out to our Quickbase Support.
Find information about connected tables
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 Historyof 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, select the user dropdown on the global bar, then select Profile. Your connections display in the My Connections area.
General errors
General errors may apply to connected tables that use any type of connection.
Error message | Possible causes | How to fix |
|---|---|---|
An unexpected error occurred. Please try again later or contact support. [QB500] | This error indicates a system issue on the Quickbase side. | Wait a few minutes and try again. If the error persists, contact Quickbase Support. |
Connect to cloud services
If you're having trouble connecting to a cloud service, here are common errors you might encounter and how to resolve them.
Error message | Possible causes | How to fix |
|---|---|---|
Authentication failed because the token cannot be refreshed. [QB401] | The token used to connect to the cloud service has expired or been revoked. | Go to your Profile page and reconnect to the service under My Connections. |
Access denied. You don't have permission to read data from [service name]. [QB403] | The account used for the connection doesn't have permission to read the specified data. | Ask the owner of the [service name] account to grant you read permission, or use a different connection that has the required permission. |
We couldn't find the data you're trying to connect to. [QB404] | The table, object, or file no longer exists in [service name], or it's been moved or renamed. | Confirm the data still exists in [service name] and hasn't been moved or renamed. If it has, update the connection to point to the new location. |
The connection was successful, but no data was returned. [QB204] | The data source is empty or your filter returned no results. | Check the connected table to confirm data exists and your filter criteria aren't too restrictive. |
The service is temporarily unavailable. Please try again later. [QB503] | [Service name] is temporarily down or experiencing issues. | Wait a few minutes and try the refresh again. If the issue continues, check the service's status page for outage information. |
The request timed out. [QB408] | The connected service took too long to respond. | Try the refresh again. If timeouts happen often, check if the source data is very large or if there are performance issues with the connected service. |
Too many requests. Please try again later. [QB429] | You've exceeded the rate limit for the connected service. | Wait before trying again, and consider reducing the frequency of your refresh schedule. |
Create a connection to Salesforce.com
If you see errors when you try to create a connection to Salesforce.com, here are some common causes and how to resolve them.
Error message | Possible causes | How to fix |
|---|---|---|
INVALID_LOGIN: Invalid username, password, security token; or user locked out. | The Salesforce.com username or password entered for the connection is incorrect, or the security token is missing or wrong. | Verify your Salesforce.com username and password are correct. Make sure you append the security token to the end of the password (for example, if your password is MyPassword and your token is TOKEN123, enter MyPasswordTOKEN123). |
LOGIN_MUST_USE_SECURITY_TOKEN: Login from untrusted IP address. A security token is required. | Your Salesforce.com org requires a security token for logins from outside the trusted IP range. | Retrieve your security token from Salesforce.com and append it to the end of your password. |
The operation is not supported for this type of org. | Connections to Salesforce.com sandbox orgs are not supported. | Use a Salesforce.com production org for the connection. Sandbox orgs are not supported. |
Connect to a table in another Quickbase app
If you see errors when you try to connect to a table in another Quickbase app, here are some common causes and how to resolve them.
Error message | Possible causes | How to fix |
|---|---|---|
Application [app name] not found. It may have been deleted, or you may not have access to it. [QB404] | The source app may have been deleted, or the connection owner may not have access to it. | Confirm the source app exists and that the connection owner has access to it. |
Table [table name] not found in the application. It may have been deleted. [QB404] | The table being connected to has been deleted from the source app. | Contact the owner of the source app to confirm the table still exists. |
The connection owner doesn't have access to the source app. [QB403] | The user who owns the connection doesn't have access to the source Quickbase app. | Ask an admin of the source app to grant the connection owner at least viewer access. |
App token required. The source app requires an app token to access its data. [QB403] | The source Quickbase app has app tokens enabled and requires a valid token for access. | On the app home page, select Settings, then select Manage Application Token. Copy and paste the app token into the App Token field. |
The app token provided is invalid. [QB403] | The app token entered does not match the token configured for the source app. | Return to the source app and copy the correct app token from Settings > Manage Application Token. |
User realm mismatch. The connection owner and source app must be in the same Quickbase account. [QB403] | The connection owner's Quickbase account is different from the account where the source app is hosted. | The connection owner must be a user in the same Quickbase account as the source app. Contact your Quickbase admin for help. |
Cross-app connected tables are not available on your current plan. [QB403] | Cross-app connected tables require a plan that supports this feature. | Contact your Quickbase account admin to upgrade your plan, or contact Quickbase Support for more information. |
Data sync failed. Too many records in the source table. [QB413] | The source table has exceeded the maximum number of records allowed for a connected table. | Add a filter to the connected table to reduce the number of records pulled from the source table. Learn more about filtering data to connect in a connected table. |
A field mapping error occurred. One or more fields in the connected table no longer exist in the source table. [QB422] | Fields that were previously mapped no longer exist in the source Quickbase table. | Go to the connected table settings and update the field mappings to remove or replace the missing fields. |
An unexpected error occurred during data sync. [QB500] |
|
|
Connect to the Admin Console
If you see errors when you try to connect to the Admin Console, here are some common causes and how to resolve them.
Error message | Possible causes | How to fix |
|---|---|---|
You don't have permission to access the Admin Console. Contact your Quickbase account admin. [QB403] | The user account used for the connection is not a Quickbase account admin. | The connection must be owned by a Quickbase account admin. Ask your admin to create the connection, or contact Quickbase Support for help. |
Connect to a folder containing CSV files
If you see errors when you try to connect to a CSV folder, here are some common causes and how to resolve them.
Error message | Possible causes | How to fix |
|---|---|---|
CSV file not found in the folder. [QB404] | No CSV files are present in the folder specified in the connection. | Confirm that the folder contains at least one CSV file, and that the folder path in the connection is correct. |
The CSV file structure has changed. [QB422] | Column headers in the CSV file have been renamed or removed since the connection was set up. | Update the connected table field mappings to match the current CSV column headers. |
Unable to parse the CSV file. The file may be corrupted or not in a valid CSV format. [QB400] | The CSV file exists but cannot be read because it's malformed. | Open the CSV file and check for formatting issues such as inconsistent delimiters, missing headers, or special characters. Re-save the file and try again. |
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, contact Quickbase Support.