Resume

type: "io.kestra.plugin.core.execution.Resume"

Resume a paused execution. By default, the task assumes that you want to resume the current executionId. If you want to programmatically resume an execution of another flow, make sure to define the executionId, flowId, and namespace properties explicitly. Using the inputs property, you can additionally pass custom onResume input values to the execution.

Examples

id: "resume"
type: "io.kestra.plugin.core.execution.Resume"
executionId: "{{ trigger.executionId }}"

Properties

executionId

• Type: string
• Dynamic: ✔️
• Required: ❌

Filter for a specific execution.

If you explicitly define an executionId, Kestra will use that specific ID.

If another namespace and flowId properties are set, Kestra will look for a paused execution for that corresponding flow.

If executionId is not set, the task will use the ID of the current execution.

flowId

• Type: string
• Dynamic: ✔️
• Required: ❌

Filter for a specific flow identifier in case executionId is set.

inputs

• Type: object
• Dynamic: ✔️
• Required: ❌

Inputs to be passed to the execution when it's resumed.

namespace

• Type: string
• Dynamic: ✔️
• Required: ❌

Filter for a specific namespace in case executionId is set. In case you wonder why executionId is not enough — we require specifying the namespace to make permissions explicit. The Enterprise Edition of Kestra allows you to resume executions from another namespaces only if the permissions allow it. Check the Allowed Namespaces documentation for more details.

Outputs

Definitions