hasura/graphql-engine · warning · NamedDataConnectorIssue

The data connector {data_connector_name} has an issue: {issu

Error message

The data connector {data_connector_name} has an issue: {issue}

What it means

Non-fatal issue wrapper for a named data connector: a DataConnectorIssue (config problem that may only be a warning depending on feature flags) is reported with the connector's qualified name.

Source

Thrown at v3/crates/metadata-resolve/src/stages/data_connectors/error.rs:49

    NdcValidationError(NDCValidationError),
    #[error(
        "The version specified in the capabilities (\"{version}\") is an invalid version: {error}"
    )]
    InvalidNdcVersion {
        version: String,
        error: semver::Error,
    },
    #[error(
        "The version specified in the capabilities (\"{version}\") is not compatible with the schema version specified. The version requirement is {requirement}"
    )]
    IncompatibleNdcVersion {
        version: String,
        requirement: semver::VersionReq,
    },
}

#[derive(Debug, thiserror::Error)]
#[error("The data connector {data_connector_name} has an issue: {issue}")]
pub struct NamedDataConnectorIssue {
    pub data_connector_name: Qualified<DataConnectorName>,
    pub issue: DataConnectorIssue,
}

impl ShouldBeAnError for NamedDataConnectorIssue {
    fn should_be_an_error(&self, flags: &flags::OpenDdFlags) -> bool {
        self.issue.should_be_an_error(flags)
    }
}

#[derive(Debug, thiserror::Error)]
pub enum DataConnectorIssue {
    #[error(
        "The version specified in the capabilities (\"{version}\") is an invalid version: {error}. Consider upgrading the data connector to the latest version to fix this."
    )]
    InvalidNdcV01Version {
        version: String,

View on GitHub (pinned to 724551b9ae)

Solutions

1. Read the inner issue detail
2. Address it (usually upgrade the connector)
3. Or relax the feature flag that escalates it to an error

Catch NamedDataConnectorIssue, consult ShouldBeAnError against your flags to decide warning vs failure, then handle the inner DataConnectorIssue.

When it happens

Trigger: Resolving a connector that has a known issue, currently invalid NDC v0.1 versions, which is escalated to an error only under certain flags.

Common situations: Running with strict/compatibility flags that turn connector issues into errors.

Related errors

• The data connector {data_connector_name} has an error: {erro
• cannot get absolute path: %w
• the aggregate expression {name} defines an aggregation funct
• the aggregate expression {name} defines an aggregation funct
• unknown data connector {data_connector:} referenced in objec

AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28). Data as JSON: /api/errors/725df19dded112fb. Report an issue: GitHub.