Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

is it possible to define subworkflow, which gets included as part of wf def

when you compile a workflow and it gets sent up to admin, the structure of any subworkflows gets automatically included

<@U0368CP47RA> yes that is the default. The closure will include the subworkflow

It is also possible to define an external subworkflow (we call it child workflow)

image a team has a well def training wf that includes hp and complex eval

they want everyone w/i their team to follow the wf pattern

think of it as defining wf templates for feature prep, data validation, data sampling, training, eval, etc

I am assuming you want to `reuse` an existing `template task / workflow` across the organization

we call it reference tasks. If you read the spotify blog they use this a lot too

<@UU43XA551> from Spotify explained it beautifully - <https://flyte-org.slack.com/archives/CNMKCU6FR/p1647335625943359?thread_ts=1647279048.028329&amp;cid=CNMKCU6FR>

you can refer to any <https://docs.flyte.org/projects/cookbook/en/latest/auto/core/flyte_basics/reference_task.html#sphx-glr-auto-core-flyte-basics-reference-task-py|task/workflow/launchplan> in the system