DAG Run

Description

This Task triggers an Airflow DAG run using this endpoint

Use Cases

Triggering an Airflow DAG from Orchestra might seem superfluous - why do I need an Orchestrator for my Orchestrator? And you'd be right - you don't. However there are a few reason why you might want to anyway;

• You work in a multi-tenanted environment where you need a single UI to trigger multiple Airflow instances

• You want Data Observability capabilities for processes being run in Airflow like monitoring Snowflake or BigQuery tables

• You are in the process of migrating off from Airflow to tools like Orchestra and want to monitor pipelines in migration and migrated pipelines from a single place

• You want to view the Airflow DAG in the context of a wider DAG

Parameters

Name	Data type	Restrictions	Example
DAG ID	String	No spaces	tutorial_dag

Error handling

API Requests

Orchestra will fail the Task if the response code isn't a 2xx code.

Code	Description	Handling
401	Unauthorised	We will raise an error and parse the raw error message from the Stitch response as the Orchestra message
404	Not Found	We will raise an error with the HTTP Reason as the Orchestra message
Other error code		We will raise an error with the HTTP Reason as the Orchestra message