Kestra

• Execution failedRuns when an execution fails, ends with warnings or is killed, of every flow, a namespace or one flow. One restarted and failing again starts it again. Executions that ended before the workflow was turned on don't.
• Execution succeededRuns when an execution succeeds, of every flow, a namespace or one flow. Executions that ended before the workflow was turned on don't start it.
• Execution stuckRuns when an execution has been running, paused, queued or waiting to start for longer than you choose, such as a load that usually takes ten minutes still running after an hour.

• List flowsList flows by namespace and ID, with each one's inputs, outputs, triggers and whether it's disabled.
• Get flowGet a flow with its YAML source, its inputs and outputs, its triggers and its webhook key.
• Create or update flowSave a flow from its YAML, as Kestra's editor does: it's created, or the flow with the namespace and ID the YAML names is updated to a new revision.
• Disable flowDisable a flow, so its schedules and other triggers start nothing until it's enabled. Executions already going carry on.
• Enable flowEnable a disabled flow, so its schedules and other triggers start executions again.
• Delete flowDelete a flow. Its past executions stay in Kestra. One that isn't there is left as it is.
• Execute flowStart an execution of a flow with the inputs and labels you give, as Kestra's Execute button does, and wait for it to end if you ask.
• Wait for executionWait until an execution ends (succeeds, fails, ends with warnings or is killed) or pauses for someone, up to 15 minutes, then get it with its outputs. One still going when the wait is up carries on in Kestra.
• Get executionGet an execution's state, inputs, labels and task runs, with the tasks that failed.
• Search executionsList executions, the latest first, by namespace, flow, state, label and when they started.
• Restart executionRun a failed or killed execution again from the tasks that didn't succeed, as Kestra's Restart button does, such as after fixing what made it fail. It keeps its ID and inputs.
• Kill executionKill an execution that hasn't ended, with the subflows it started. One that has ended is left as it is.
• Pause executionPause a running execution: tasks running now finish, and no new ones start until it's resumed. One that isn't running is left as it is.
• Resume executionResume a paused execution, such as one waiting for an approval, with the inputs its Pause task asks for. One that isn't paused is left as it is.
• Replay executionStart a new execution from an old one, with the same inputs, from its first task or the task you name, as Kestra's Replay does. The old one stays as it is.
• Delete executionDelete an execution that has ended, with its logs, metrics and files. One that isn't there is left as it is.
• Get execution logsGet an execution's log, its last lines oldest first, with the last error it logged.
• Get execution outputsGet the outputs an execution's flow gives, and those of each task, such as a row count or a file's address.
• List namespacesList Kestra's namespaces by name, those with flows and those holding them.
• Get KV pairGet the value of a KV pair in a namespace's KV store, which flows read with kv().
• Set KV pairSet a KV pair in a namespace's KV store, such as a date to load from, making it if there's none.
• Delete KV pairDelete a KV pair from a namespace's KV store. One that isn't there is left as it is.
• Send to webhookSend data to a flow's Webhook trigger, which starts an execution that reads it as trigger.body. The flow needs a Webhook trigger.

No actions match that.