View

Search – DAG Runs

Filters to Add

• Filter by DAG ID

  ↪ Useful when triaging DAGs across environments or viewing all runs for a specific DAG without switching views

• Filter by Run ID
  ↪ Useful for debugging across views and linking from external systems or audit logs

• Filter by Start Date
  ↪ Helps find DAG runs that started within a specific time window (e.g., peak load periods)

• Filter by End Date
  ↪ Useful for spotting recently completed runs or identifying DAGs that finished during outages or incidents

• Filter by Duration Range
  ↪ Identify slow or long-running DAGs to tune performance or spot issues with stuck tasks

• Filter by DAG Version and/or Bundle Version
  ↪ Correlate failures or behavioral changes with code changes over time

• Filter by Conf Content
  ↪ Search for runs where conf contains specific keys or values (e.g., for dynamic configuration or user-specific logic)

• Filter by Triggered By
  ↪ Distinguish manual runs, asset-triggered runs, CLI-triggered runs, or other automated triggers; important in hybrid scheduling

• Filter by Producing Asset
  ↪ Show runs created as a result of an upstream asset event, useful for event-driven DAGs and lineage debugging

• Filter by **Logical Date ** or Run After (Range)
  ↪ Logical Date is the canonical “execution date” and is often used for backfill or partitioned logic; “Run After” helps with when something is scheduled to run, independent of the logical date

API Support

⚠️ Partial

• /dagRuns supports query params:
  • dag_id, execution_date, state, run_type
• Missing support for:
  • Duration range
  • DAG version / bundle version - add dag_version filter to get_dag_runs endpoint and corresponding tests #54882
  • Trigger source
  • Conf keys/values
  • Producing asset (currently not modeled)

Would require API enhancements to support full filter set.

UI Impact

• Filters should appear at top of the Search – DAG Runs screen
• Should use consistent UX patterns (e.g., date range pickers, tag-like selectors)