Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

taskReferenceName needs to be unique within a workflow #2662

Discussion options

You must be logged in to vote

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.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by shahnaresh41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
2 participants
Converted from issue

This discussion was converted from issue #2635 on December 20, 2021 22:52.