@ancient-wolf-19325 why is my workflow name using src.workflows.<blah> How is the workflow name generated?

Flyte generates workflow names by default using the Python module path and function name, resulting in names like

src.workflows.<workflow_name>

. This is because Flyte derives the name from the file and function where the workflow is defined, which helps ensure uniqueness across projects and modules. For example, if your workflow is defined in

src/workflows/example.py

as

@workflow def my_wf(): ...

, the registered name will be

src.workflows.example.my_wf

(source, source, source). Currently, there is no officially documented way to override the workflow name at registration time using a decorator parameter (unlike tasks, which can use

.with_overrides(name="...")

at invocation). Feature requests exist to allow a

name

parameter for workflows, but as of now, the default naming is based on the module and function (source, source). Would you like more detail on possible workarounds or future plans for custom workflow naming? Sources: - Flyte core concepts: workflow naming - GitHub Issue: workflow name generation - GitHub Issue: allow user named workflows - GitHub Issue: nicknames for Flyte constructs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how do I use

.with_overrides(name="...")

to override task names

You can use

.with_overrides(name="...")

when invoking a task inside a workflow to override the display name of that specific task node in the workflow execution. For example:

my_task().with_overrides(name="custom_task_name")

(source). Note that this only changes the node's display name in the workflow UI and does not affect the registered task's canonical name. You can also override the DAG node name using

node_name="..."

in

.with_overrides

. Would you like a step-by-step example or more details? Sources: - Flyte: Overriding parameters with with_overrides 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.