Skip to content

Creating Batch Inference Pipeline from successful job often results in 'UserError: An item with the same key has already been added. Key: [Node info]' #10

@mkrasmus

Description

@mkrasmus

Having successfully completed a successful job training a model in designer I have been getting error messages when trying to create a batch inference pipeline. The most recent relates to one designer component to create indicator variables. The batch inference pipeline job fails to create the TD and throws out a "An item with the same key has already been added. Key: Indicator_values_transformation". This has happened before with a cleaning data transformation step, which I needed to remove. The validate button does not pick up on any issue with respect to this which is also puzzling - if node information naming convention is limited to no duplication across components then a simple fix would be to ensure the validator picks up on this error. An example of the most recent error message is:

UserError
An item with the same key has already been added. Key: Indicator_values_transformation
Properties
Stack trace
Error: Request failed with status code 400
    at e.exports (https://ml.azure.com/static/js/index.4c6d02e5.chunk.js:2:3161896)
    at Soal.e.exports (https://ml.azure.com/static/js/index.4c6d02e5.chunk.js:2:1999144)
    at XMLHttpRequest.y (https://ml.azure.com/static/js/index.4c6d02e5.chunk.js:2:1079868)
Target
-
Client request ID
4058b1f6-0d44-4408-ba3a-4f451a4c1298
Trace ID
66ed3c4b-3246-4ad9-9869-e87a87228909
Service request ID
-

YAML

{
  "error": {
    "code": "UserError",
    "message": "An item with the same key has already been added. Key: Indicator_values_transformation",
    "additionalInfo": null,
    "details": []
  },
  "correlation": {
    "operation": "61ae723306a24d1b9db01e4f723d4beb",
    "request": "8337dcab96838c3b"
  }
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions