New RunLLM response generated: >>>*# Question* This is a minor detail. Registering workflows with the same version gives the same message. If I run this command twice

pyflyte register myworkflowpy -p test -d development --version "1234567"

I will get the same message both times

Registration ..... type TASK successful with version 1234567

which kind of implies that it was overwritten or re-registered. However the registered workflow is immutable and the timestamp on the 123467 version does not change. A better message would that the attempted registration

{Project, Domain, Name, Version}

already exists # Answer Flyte workflows are immutable once registered with a specific

{Project, Domain, Name, Version}

combination. Re-registering a workflow with the same version does not update the existing workflow, and the timestamp remains unchanged. The current message can be misleading as it implies the workflow was re-registered. To improve clarity, the message should indicate that the workflow already exists. This behavior is confirmed by the Flyte documentation and community discussions (source). Would you like more details on how to handle this or any other aspect of Flyte? Sources: - Flyte Community Discussion Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1724193501.320829 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.