Flow Dag

Flow Dag

Certified

Define tasks as a DAG with explicit dependencies.

Declare tasks and their dependsOn links; Kestra derives the execution order and parallelism (bounded by concurrent). Tasks may only reference peers inside this DAG block.

UI low-code forms are disabled for now with DAG tasks.

yaml
type: io.kestra.plugin.core.flow.Dag

Run a series of tasks for which the execution order is defined by their upstream dependencies.

yaml
id: dag_flow
namespace: company.team
tasks:
  - id: dag
    type: io.kestra.plugin.core.flow.Dag
    tasks:
      - task:
          id: task1
          type: io.kestra.plugin.core.log.Log
          message: task 1
      - task:
          id: task2
          type: io.kestra.plugin.core.log.Log
          message: task 2
        dependsOn:
          - task1
      - task:
          id: task3
          type: io.kestra.plugin.core.log.Log
          message: task 3
        dependsOn:
          - task1
      - task:
          id: task4
          type: io.kestra.plugin.core.log.Log
          message: task 4
        dependsOn:
          - task2
      - task:
          id: task5
          type: io.kestra.plugin.core.log.Log
          message: task 5
        dependsOn:
          - task4
          - task3
Properties
Min items1
Definitions
task*

The task within the DAG

dependsOnarray
SubTypestring

The list of task IDs that should have been successfully executed before starting this task

Assets this task consumes as inputs or produces as outputs, for lineage tracking and the asset graph (Enterprise Edition). A flow declaring this property on a task is rejected in the open-source edition.

Definitions
assetFailureBehaviorstring
Possible Values
IGNOREFAILWARN

Asset failure behavior

Behavior applied to the task state when a declared asset fails to render, emit, or be persisted (e.g. a lock conflict): FAIL escalates it to FAILED, WARN (default) warns it if it would otherwise succeed, IGNORE leaves the state untouched.

enableAutobooleanstring

Whether to auto-register assets referenced dynamically at runtime that are not statically declared in inputs or outputs.

inputsarray

The assets consumed as inputs.

id*string
Min length1
typestring
outputs

The assets produced as outputs.

id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*string
Min length1

Custom asset type

descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
Default0

Number of concurrent parallel tasks that can be running at any point in time

If the value is 0, no concurrency limit exists for the tasks in a DAG and all tasks that can run in parallel will start at the same time.

List of tasks to run if any tasks failed on this FlowableTask.

DefaultFAIL
Possible Values
CONTINUECANCELFAILUNKNOWN

What to do with the other still-running tasks when one task fails.

CONTINUE: other tasks keep running to completion, as today.

CANCEL / FAIL (default): as soon as a task fails with no retry left, every other still-running task in this DAG is interrupted and lands in the given state. The DAG itself still resolves to FAILED and its errors/finally tasks still run normally.

More Plugins in this Category

Bun
Bun

Tasks that run Bun scripts.

DataCore

4 tasks

PHP
PHP

Tasks that run PHP scripts.

Core

4 tasks