Reconnecting to a Data Connector

Reconnect instantly fixes Data Connector connectivity issues by simply reinitializing the session without altering the saved configuration.

Use Reconnect to re-establish connectivity for a Data Connector after credential updates, network changes, or transient failures. Reconnect re-tests and re-initializes the session without changing the connector’s saved configuration.

When to use Reconnect

• Password/API key was rotated or refreshed.

• Source network/VPN/firewall changed.

• The connector shows an error or disconnected status.

• After fixing connectivity settings outside the platform (e.g., DB allowlist updated).

Steps

1. Navigate to the Standard Connectors list.

2. Select the Data Connector you want to re-establish.

3. Click the Reconnect icon for the selected connector.

• A confirmation message appears, and the selected Data Connector gets reconnected.

Notes & tips:

• Reconnect does not modify connector settings (host, port, credentials). Use Edit if you need to change them, then Save and Reconnect if prompted.

• After reconnecting, open a dependent Dataset or Data as API and run a quick query/test to validate end-to-end access.

• If your connector supports a Test Connection action, use it before/after reconnect to confirm status.

Troubleshooting

• Reconnect icon disabled: Ensure you have permission on this connector, or the connector is not already in a healthy state that disallows reconnect.

• Reconnect succeeds but queries fail: Verify database/schema privileges, network allowlists, and that credentials are current.

• Persistent failure: Edit the connector, re-enter credentials or TLS/SSL options, Save, then Reconnect. Check VPN/proxy/firewall rules.

• Downstream errors remain: Refresh/retry the dependent Dataset, Data Store, or Data as API; some assets may cache connections.