Connection test failed
Verify the hostname, port, database, username, password, SSL mode, and network access. For a private database, follow Private database access.Schema discovery returned no streams
Confirm that the source user can read the expected schema or API resources. For HubSpot, verify the required token permissions in the connector reference.Connector card is disabled
Strapi, Zendesk, and DuckDB connections are Coming Soon. Their disabled catalog cards are expected and cannot be enabled by refreshing or reconnecting. Choose an Available Now connector from Connections Overview.Data Preview is empty
Confirm that the selected stream contains records and that the current connection can read them. Refresh discovery before retrying when the source schema changed.SQL validation failed
Check the source reference, selected columns, and SQL syntax. The model output columns must match the pre-created destination table. See SQL Layer.Pipeline Run failed before delivery
Common causes include:- the source table or stream is no longer available;
- source or destination permissions changed;
- the destination table does not exist;
- the SQL output contains a column missing from the destination table;
- Incremental sync is missing a valid replication key; or
- the workspace reached a plan limit.