Errors and Warnings on DataSet Details page

Errors and warnings on the Dataset Details page

Errors and warnings for a dataset are surfaced directly at the top of the Dataset Details page — above the Sync Details, Data Checks, and Lineage tabs — so you can see the dataset's current health without opening the lineage graph.

⚠️

A warning is not an error

Warnings are informational. They flag conditions you may want to be aware of — most commonly that a dataset is not account matched or not date matched. A warning does not mean the dataset is broken, and it does not always require action.

If account matching or date matching isn't relevant to how you're using the dataset, you can safely ignore the warning. For example, if your workflow doesn't depend on account-level joins, a "not account matched" warning is just a notice — no fix needed.

Errors, by contrast, indicate a broken or invalid dependency and typically need to be resolved before the dataset can be used reliably downstream.

Warnings and errors reflect the state of your data as of the last time it was received — not your current configuration. If you've recently updated a mapping or setting, trigger a sync to refresh the messages.

Common Data Cloud connector errors and what to do

When you build or update a connector/dataset, you may see one of the messages below. Here's what each means and whether you can resolve it yourself.

"We have not yet received data"

The connector hasn't received any data yet. What to do: send at least one event or test record from your source (for example, from your Zapier integration) so the connector has data to work with, then try again.

"Your Connection or SQL is invalid"

For SQL-based connectors, this means the connection details or the SQL query you provided could not be validated. What to do: double-check your credentials and review your SQL query for errors, then retry.

"Unknown network id" / a referenced source can't be found

The data source or network the connector points to can't be found — it may have been deleted, or your access to it may have changed. What to do: re-select a valid data source for the connector.

"…is not a supported import provider"

The selected provider can't be used for this type of import mapping. What to do: use a supported import source for this workflow.

Errors that mention custom dimensions/metrics couldn't be retrieved

This can happen if the integration's authorization has expired, or due to a temporary issue on the data source's side. What to do: try reconnecting the integration. If the problem persists, contact NinjaCat support.

Errors mentioning providers, SQL identifiers, or "contact support"

Some errors point to internal configuration that isn't something you can change yourself (for example, messages about an unsupported provider, a data catalog provider not being found, or SQL identifier issues). What to do: contact NinjaCat support — these need to be handled on our side.