Skip to content

Clarify the structure and usage of run.workflow for sub-workflows #1122

@treblereel

Description

@treblereel

I tried this:

Description:
In the schema, there is a run.workflow element that defines a sub-workflow.
However, it’s not entirely clear how this definition is supposed to be used.

The workflow definition currently specifies the following properties:

  • namespace
  • name
  • version
  • input

As I understand it, a sub-workflow should behave similarly to a regular workflow — meaning it should at least contain a do definition or some equivalent execution logic.

It would be helpful to clarify:

  • whether a sub-workflow must include its own do section,
  • how it inherits or overrides inputs/outputs,
  • and how its execution context is handled relative to the parent workflow.

- title: RunWorkflow

This happened:

I can define sub-workflow

I expected this:

No response

Is there a workaround?

No response

Anything else?

No response

Area(s)

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions