hasura/graphql-engine · error · InternalDeveloperError

Argument mapping not found for the argument {argument_name:}

Error message

Argument mapping not found for the argument {argument_name:} while executing the relationship {relationship_name:}

What it means

Thrown when executing a relationship whose argument mapping requires argument_name, but no mapping entry for that argument could be resolved. Relationship argument mappings bind GraphQL arguments to source fields or literals; a missing binding cannot be defaulted safely.

Source

Thrown at v3/crates/graphql/ir/src/error.rs:214

        type_name: Qualified<CustomTypeName>,
        field_name: FieldName,
    },

    #[error("Object type '{type_name}' not found")]
    ObjectTypeNotFound {
        type_name: Qualified<CustomTypeName>,
    },

    #[error("The field '{field_name}' was not found on object type '{object_type_name}'")]
    ObjectTypeFieldNotFound {
        field_name: FieldName,
        object_type_name: Qualified<CustomTypeName>,
    },

    #[error("{0}")]
    RelationshipFieldMappingError(#[from] plan::RelationshipFieldMappingError),

    #[error(
        "Argument mapping not found for the argument {argument_name:} while executing the relationship {relationship_name:}"
    )]
    ArgumentMappingNotFoundForRelationship {
        relationship_name: RelationshipName,
        argument_name: ArgumentName,
    },

    #[error(
        "The aggregation function {aggregation_function} operating over the {aggregate_operand_type} type is missing a data connector mapping for {data_connector_name}"
    )]
    DataConnectorAggregationFunctionNotFound {
        aggregate_operand_type: QualifiedTypeName,
        aggregation_function: AggregationFunctionName,
        data_connector_name: Qualified<DataConnectorName>,
    },

    #[error(
        "A field ({field_name}) with an AggregatableField annotation was found on a scalar-typed ({aggregate_operand_type}) operand's selection set"

View on GitHub (pinned to 724551b9ae)

Solutions

1. Add the missing argument mapping for argument_name in the relationship metadata
2. Regenerate the relationship metadata with the CLI instead of hand-editing
3. Ensure every argument the relationship declares has a corresponding mapping

# CLI/metadata check: assert every argument in the relationship has an argument mapping
hasura validate metadata

// Catch during planning; report which relationship/argument is unmapped to guide metadata fix

When it happens

Trigger: A relationship defined with argument mappings where one declared argument has no mapping entry; passing an argument to a relationship that the metadata does not map; metadata hand-edited and missing the argument_mapping for one argument.

Common situations: Hand-writing or transforming metadata files and dropping an argument mapping; upgrading metadata format versions where argument mappings must be explicit.

Related errors

• Couldn't find relationship ${field.relationship} for field $
• Field mapping not found for the field {field_name:} of type
• Object type '{type_name}' not found
• the following data connector arguments are not mapped to an
• Cannot add query root field {0} as it already in use

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