hasura/graphql-engine · error · DataConnectorScalarTypesError::GraphqlConfigError
{0}
Error message
{0} What it means
Transparent wrapper in the data-connector-scalar-types stage for GraphqlConfigError. It surfaces GraphQL configuration problems (e.g. duplicate names, invalid field names) encountered while deriving connector scalar types.
Source
Thrown at v3/crates/metadata-resolve/src/stages/data_connector_scalar_types/error.rs:30
None
}
}
#[derive(Debug, thiserror::Error)]
pub enum DataConnectorScalarTypesError {
#[error(
"multiple type representations defined for scalar {scalar_type:} from data connector {data_connector:}"
)]
DuplicateDataConnectorScalarRepresentation {
data_connector: Qualified<DataConnectorName>,
scalar_type: DataConnectorScalarType,
},
#[error("unknown type represented for scalar type {scalar_type:}: {type_name:}")]
ScalarTypeUnknownRepresentation {
scalar_type: DataConnectorScalarType,
type_name: Qualified<CustomTypeName>,
},
#[error("{0}")]
GraphqlConfigError(#[from] graphql_config::GraphqlConfigError),
#[error("{0}")]
ScalarBooleanExpressionTypeError(
#[from] scalar_boolean_expressions::ScalarBooleanExpressionTypeError,
),
}
View on GitHub (pinned to 724551b9ae)
Solutions
- Read the inner GraphqlConfigError message
- Fix the graphql configuration for the affected type
- Rebuild metadata
Defensive patterns
Strategy: try-catch
Try / catch
Catch and delegate to the inner GraphqlConfigError's handling.
Prevention
- Use a graphql config linter for type/scale naming rules
- Test metadata builds on every config change
When it happens
Trigger: Resolving connector scalar types when the metadata's graphql configuration for a type is invalid.
Common situations: Bad graphql config block on a scalar/type definition in metadata.
Related errors
- setting up codegen-assets repo failed (this is required for
- {0}
- {0}
- multiple type representations defined for scalar {scalar_typ
- unknown type represented for scalar type {scalar_type:}: {ty
AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28).
Data as JSON: /api/errors/9139365aa6b01b72.
Report an issue: GitHub.