{"record":{"id":"a0fdd2d5a8d91ec3","repo":"hasura/graphql-engine","slug":"0-a0fdd2","errorCode":null,"errorMessage":"{0}","messagePattern":"\\{0\\}","errorType":"exception","errorClass":"RelationshipError","httpStatus":null,"severity":"error","filePath":"v3/crates/metadata-resolve/src/stages/object_relationships/error.rs","lineNumber":174,"sourceCode":"    ValueExpressionMappingsNotSupportedYet,\n    #[error(\n        \"The field path provided in the {location:} of the relationship {relationship_name} on type {type_name} is empty\"\n    )]\n    EmptyFieldPath {\n        location: String,\n        relationship_name: RelationshipName,\n        type_name: Qualified<CustomTypeName>,\n    },\n    #[error(\n        \"Model fields cannot be used in command based relationship: {relationship_name:} on type {type_name:}\"\n    )]\n    ModelFieldCannotBeUsedInCommandRelationship {\n        relationship_name: RelationshipName,\n        type_name: Qualified<CustomTypeName>,\n    },\n    #[error(\"Relationships with nested field paths are not supported yet.\")]\n    NestedFieldPathsNotSupportedYet,\n    #[error(\"{0}\")]\n    CommandError(#[from] commands::CommandsError),\n    #[error(\"{0}\")]\n    ModelError(#[from] models::ModelsError),\n    #[error(\"{0}\")]\n    GraphqlError(#[from] graphql_config::GraphqlConfigError),\n}\n","sourceCodeStart":156,"sourceCodeEnd":181,"githubUrl":"https://github.com/hasura/graphql-engine/blob/724551b9ae87845594ef0408cff0e50eb6c90dc5/v3/crates/metadata-resolve/src/stages/object_relationships/error.rs#L156-L181","documentation":"A transparent wrapper (#[from] conversion) around an error from the commands resolution stage (CommandsError). The relationship resolver delegates to command metadata resolution and any failure there is surfaced unchanged via this variant.","triggerScenarios":"Any error while resolving command metadata referenced by a relationship — unknown types in command arguments/output, invalid command names, or other command-level validation failures.","commonSituations":"Command metadata problems that only surface when a relationship pulls that command into resolution; editing commands and relationships together where the command part is broken.","solutions":["Treat this as the inner CommandsError — read the wrapped message to identify the actual command problem","Fix the command metadata (types, names, arguments) that the inner error points to","Re-run resolution; the relationship error disappears once the command resolves cleanly"],"exampleFix":null,"handlingStrategy":"try-catch","validationCode":null,"typeGuard":null,"tryCatchPattern":"try { await applyMetadata(md); } catch (e) { if (String(e).includes('relationship') && /command/i.test(e.cause?.message ?? '')) { /* handle underlying CommandsError from e.cause */ } throw e; }","preventionTips":["Resolve command metadata independently first so inner errors are caught earlier","Keep command and relationship changes in the same change set and test together"],"tags":["metadata","relationships","command","wrapper","delegate"],"backgroundTag":"metadata-relationship-validation-failed","analyzedSha":"724551b9ae87845594ef0408cff0e50eb6c90dc5","analyzedAt":"2026-08-28T07:32:55.105Z","schemaVersion":2},"datasetVersion":"2026-08-28T11:17:15.048Z"}