A data connection is failing
When a connection that syncs on a schedule stops syncing, dashboards and the assistant keep the data that was already synced, but they don't get new data. Start in the Data Catalog: the Status column shows what's wrong, and the menu on each connection has the actions you need.
Read the status
| Status | What it means |
|---|---|
| Failed | The last sync didn't finish. Hover over the status to see the reason. |
| Test failed | Qubit couldn't reach the source with the saved settings. |
| Reconnect needed | The app's authorization has expired, so syncing has stopped. |
| Expires in N days | The app's authorization expires soon. Syncing stops when it does. |
| Synced, no data received | The sync finished, but the source returned no rows. |
1. The password or key changed
If someone changed the password or key that Qubit uses, the connection fails.
- In the Data Catalog, open the menu on the connection and click Edit.
- Enter the new credentials and save.
- Click Test connection, then Sync now.
2. The app needs to be reconnected
Apps such as ad platforms use an authorization that expires. When you see Reconnect needed or Expires in N days, click Edit on the connection and connect the account again. Data that was already synced isn't affected.
3. The database blocks Qubit
If your database only accepts connections from approved networks, Qubit can't reach it until your IT team allows it. Contacting support if your IT team needs details about how Qubit connects.
For some databases, you can instead reach the database through an SSH server on your network with Connect via SSH tunnel. This option is only offered when you add a new connection. Connections made this way run queries directly against the database and don't copy the data into Qubit.
4. The sync finished with no data
If the status is Synced, no data received, the source returned no rows. Check that the account Qubit uses has data and has permission to read it, and check any filters in the connection settings. The data you already had stays in place, and the next scheduled sync runs as usual.
If the connection's tables show Some tables did not sync, Qubit couldn't read some tables. Check the database permissions for those tables and sync again.
5. Still failing
If the connection still fails after you've checked the credentials and network access, contact support. Include the connection name and the error shown when you hover over its status.