Skip to main content

Transfer orchestration task attributes to assets
App

You can use the Orchestration tasks attribute transfer app to propagate operational attributes from orchestration tasks and jobs (such as run status, schedules, and Atlan links) to directly connected upstream or downstream assets through Atlan lineage.

Prerequisites​

Before you begin, make sure you have:

  • Access to the Orchestration tasks attribute transfer app. Verify access by searching for Orchestration tasks attribute transfer in the Atlan marketplace. If you don't have access, contact Atlan support or your Atlan customer team to request it.
  • At least one orchestration connection (Airflow, MWAA Airflow, Astronomer Airflow, Google Cloud Composer Airflow, or Spark) crawled in Atlan with tasks or jobs already available.
  • A custom metadata set with one property per attribute to transfer. See Create custom metadata below.

Create custom metadata​

The app writes task and job attributes into a custom metadata set on target assets. Create this set before configuring the workflow.

  1. In Atlan, go to Governance and select Custom Metadata.

  2. Click Add custom metadata, enter a name, and save. Note this name. It goes into Custom metadata name during workflow configuration.

    Example: OL Task

  3. Add one property for each attribute to transfer, using the required property type:

    AttributeProperty type
    Run StatusText
    Run End TimestampText
    Task ScheduleText
    Task Atlan LinkURL
    DAG Atlan LinkURL

  4. Optionally, restrict each property to the asset types you want to target.

Configure workflow​

  1. In your Atlan workspace, go to the homepage and click New workflow in the top navigation bar.

  2. Search for Orchestration tasks attribute transfer, and then select Set up workflow.

  3. In Workflow name, enter a descriptive name to identify this workflow run.

    Example:

    prod-airflow-task-attribute-transfer

  4. In Connector names, select the connectors whose tasks and jobs serve as the source. Select all connectors that apply to your environment.

  5. In Custom metadata name, enter the exact name of the custom metadata set created in Create custom metadata.

    Example:

    OL Task

  6. In Transfer direction, select how the workflow traverses lineage from matched tasks and jobs:

    • Downstream: Propagates attributes to output assets (assets that receive data from the task).
    • Upstream: Propagates attributes to input assets (assets that feed data into the task).

    The workflow evaluates only direct connections at depth-1 and ignores connections, processes, and DAGs during lineage traversal.

  7. For each attribute to transfer, add an Attribute name and Custom metadata property name pair:

    • Select an attribute from the Attribute name dropdown.
    • Enter the matching custom metadata property name in Custom metadata property name.
    • Repeat for each attribute.

    Example:

    Attribute nameCustom metadata property name
    Run StatusTask Status
    Run End TimestampLast Run Time
    Task Atlan LinkTask URL

  8. In Source filters, optionally add filters to limit which tasks and jobs the workflow processes. 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.

  9. In Target filters, optionally add filters to limit which upstream or downstream assets receive the transferred attributes. Leave this section empty to propagate attributes to all qualifying assets.

  10. Click Run to start the workflow.

Validate results​

After the workflow completes:

  1. Navigate to an upstream or downstream asset that the workflow updated.
  2. Open the asset's Properties or Custom metadata panel.
  3. Verify the transferred attributes (such as Task Status or Last Run Time) appear with values from the source task or job.

If custom metadata properties don't appear, confirm the custom metadata set name and property names match exactly what was entered in the workflow configuration.

See also​