taskReferenceName needs to be unique within a workflow #2662
-
Moving from conductor-2.30.0 to 3.3.4 and trying to import old workflow definition to conductor-3.3.4 Error :{ |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The constraint that taskReferenceName needs to be unique in a given workflow was always implicit within Conductor, but was only enforced in v2.5.0 . This was a necessary validation because task reference names are used to wire inputs and outputs of tasks within the workflow. If the task reference names are not unique, then the JSON parser will not be able to correctly evaluate these expressions/wiring payloads between tasks. |
Beta Was this translation helpful? Give feedback.
The constraint that taskReferenceName needs to be unique in a given workflow was always implicit within Conductor, but was only enforced in v2.5.0 .
This was a necessary validation because task reference names are used to wire inputs and outputs of tasks within the workflow. If the task reference names are not unique, then the JSON parser will not be able to correctly evaluate these expressions/wiring payloads between tasks.