## Orchestration tasks attribute transfer

URL: https://docs.atlan.com/product/capabilities/lineage/references/orchestration-tasks-attribute-transfer

> Complete configuration reference for the Orchestration tasks attribute transfer app, including connector selection, custom metadata mapping, transfer direction, and filter options.

<!--vale off-->

# Orchestration tasks attribute transfer 

<!--vale on-->

The Orchestration tasks attribute transfer app propagates selected attributes from orchestration tasks and jobs to directly connected upstream or downstream assets using Atlan lineage at depth-1. It evaluates tasks and jobs matching configured connector and source filters, then writes attributes such as run status, schedules, and Atlan links into custom metadata properties on qualifying target assets. This reference provides complete configuration details for the Orchestration tasks attribute transfer app.

## Access

The Orchestration tasks attribute transfer app is disabled by default. To use this app, [**contact Atlan support**](https://docs.atlan.com/support/submit-request) and request it be added to your tenant.

## Prerequisites

A custom metadata set with one property per attribute to transfer must exist in Atlan. For step-by-step setup, see [Transfer orchestration task attributes to assets](https://docs.atlan.com/llms/catalog/lineage/transfer-orchestration-task-attributes/llms.txt).

## Configuration

This section defines the fields required for workflow setup.

### Workflow name

Specifies a unique and descriptive name to identify this workflow configuration in the Atlan interface. This name appears in the workflow list and helps distinguish it from other propagation workflows.

_Example:_

```text
prod-airflow-task-attribute-transfer
```

### Connector names

Selects the connectors whose tasks and jobs serve as the source for attribute propagation. Only tasks and jobs belonging to the selected connectors are evaluated during the lookup.

Supported connectors:

- Airflow
- MWAA Airflow
- Astronomer Airflow
- Google Cloud Composer Airflow
- Spark

Select all connectors relevant to your orchestration environment.

### Custom metadata name

Specifies the name of the custom metadata set that stores transferred attributes on target assets. This value must exactly match the name of the custom metadata set created in [**Prerequisites**](#prerequisites).

_Example:_

```text
OL Task
```

### Transfer direction

Controls whether the workflow traverses lineage to reach downstream or upstream assets from matched tasks and jobs. The workflow operates at depth-1 only, selecting direct input or output assets.

The workflow ignores connections, processes, and DAGs when traversing lineage.

- **Downstream**: Selects output assets of each matched task or job (assets that directly receive data from the task).
- **Upstream**: Selects input assets of each matched task or job (assets that directly feed data into the task).

### Attribute name and custom metadata property name

Maps each task or job attribute to a corresponding property in the custom metadata set. Select one attribute from the **Attribute name** dropdown, then enter the matching custom metadata property name in **Custom metadata property name**. Repeat for each attribute to transfer.

Supported attributes:

| Attribute | Description |
|---|---|
| Run Status | Current execution status of the task or job |
| Run End Timestamp | Timestamp of the last completed run |
| Task Atlan Link | URL linking to the task asset page in Atlan |
| Task Schedule | Configured schedule expression for the task or job |
| DAG Atlan Link | URL linking to the DAG asset page in Atlan |

*Example mapping:*

| Attribute name | Custom metadata property name |
|---|---|
| Run Status | Task Status |
| Run End Timestamp | Last Run Time |
| Task Atlan Link | Task URL |

## Source filters

Applies filters to tasks and jobs in the selected connectors. Only tasks and jobs matching all configured filters have their attributes propagated. Leave this section empty to include all tasks and jobs in the selected connectors.

Each filter requires an operator and a value. The workflow applies a filter only when both fields are filled in. The exceptions are **Is Empty** and **Isn't Empty**, which don't require a value.

| Filter | Description |
|---|---|
| Name | Filters tasks and jobs by asset name |
| Certificate | Filters by certification status (for example, Verified or Deprecated) |
| Qualified Name | Filters by the full qualified name of the task or job |
| Description | Filters by description text |
| Announcement | Filters by announcement type or message |

## Target filters

Applies filters to upstream or downstream assets identified by the transfer direction. Attributes transfer only to assets matching all filters defined here. Leave this section empty to transfer attributes to all qualifying upstream or downstream assets.

Each filter requires an operator and a value. The workflow applies a filter only when both fields are filled in. The exceptions are **Is Empty** and **Isn't Empty**, which don't require a value.

| Filter | Description |
|---|---|
| Connection | Filters target assets by source connection |
| Name | Filters by asset name |
| Certificate | Filters by certification status |
| Qualified Name | Filters by the full qualified name of the target asset |
| Description | Filters by description text |
| Announcement | Filters by announcement type or message |

## See also

- [Transfer orchestration task attributes to assets](https://docs.atlan.com/llms/catalog/lineage/transfer-orchestration-task-attributes/llms.txt): Step-by-step guide for configuring and running the Orchestration tasks attribute transfer app.
- [Alert propagation](https://docs.atlan.com/llms/catalog/lineage/alert-propagation/llms.txt): Reference for propagating alert and incident metadata through lineage to downstream assets.
- [Lineage Builder](https://docs.atlan.com/llms/catalog/lineage/lineage-builder/llms.txt): Reference for creating lineage relationships between assets using CSV imports.

---