Delete execution information

Description

The Delete execution information action removes stored executions from an execution information location.

Place it in a workflow that you run on a schedule when a location should not keep every run. The action deletes execution information only. The location metadata stays, so later runs can keep writing to it.

Options

Option	Description
Action name	The name of the workflow action.
Execution information location	The location to clean. The name can be chosen from the locations in the project.
Older than	Executions that started longer ago than this are deleted. Use a positive number. A variable is allowed.
Unit	Minutes, hours, days, weeks, or months.
Delete all executions in this location	When this is on, the age is ignored and every execution in the location is deleted.

Option

Description

Action name

The name of the workflow action.

Execution information location

The location to clean. The name can be chosen from the locations in the project.

Older than

Executions that started longer ago than this are deleted. Use a positive number. A variable is allowed.

Unit

Minutes, hours, days, weeks, or months.

Delete all executions in this location

When this is on, the age is ignored and every execution in the location is deleted.

An execution with no start date is deleted together with the ones that are old enough. Children of a deleted execution are removed with it.

Result

What this action passes on to the next action. See Action results for how results travel through a workflow.

Result	Value
True	The executions were deleted, with 0 errors. No execution to delete, or a root folder that doesn’t exist yet, is also true. The result is not used for hops: see the WARNING.
False	The number of errors is 1. Execution information location is empty or doesn’t exist, Older than is empty, 0, negative or not a number while Delete all executions in this location is unchecked, or an execution can’t be deleted (for example a read-only folder).
Result files	Passed on unchanged.
Result rows	Passed on unchanged.
Lines deleted	The number of executions deleted. A File location counts each run once, with everything it ran (child pipelines, actions, transforms). A Caching file location counts the workflow and each pipeline it ran separately. When the action is false, the value of the previous action is passed on.

Result

Value

True

The executions were deleted, with 0 errors. No execution to delete, or a root folder that doesn’t exist yet, is also true. The result is not used for hops: see the WARNING.

False

The number of errors is 1. Execution information location is empty or doesn’t exist, Older than is empty, 0, negative or not a number while Delete all executions in this location is unchecked, or an execution can’t be deleted (for example a read-only folder).

Result files

Passed on unchanged.

Result rows

Passed on unchanged.

Lines deleted

The number of executions deleted. A File location counts each run once, with everything it ran (child pipelines, actions, transforms). A Caching file location counts the workflow and each pipeline it ran separately. When the action is false, the value of the previous action is passed on.

A success or failure hop from this action is never followed, whatever the result: only an unconditional hop is. The result and the metrics are still passed on to the next action.

A Caching file location only deletes the executions of the project the workflow runs in, when both have a project id: an execution stored without project id is deleted from any project, and a workflow that runs in a project without project id deletes the executions of every project. A File location deletes the executions of every project that writes to it.