Skip to content

Fix Dag detail page 500 for Dags without a fileloc #69035#69110

Open
haseebmalik18 wants to merge 1 commit into
apache:mainfrom
haseebmalik18:fix-dag-detail-500-null-fileloc
Open

Fix Dag detail page 500 for Dags without a fileloc #69035#69110
haseebmalik18 wants to merge 1 commit into
apache:mainfrom
haseebmalik18:fix-dag-detail-500-null-fileloc

Conversation

@haseebmalik18

@haseebmalik18 haseebmalik18 commented Jun 28, 2026

Copy link
Copy Markdown
Contributor

DagModel.fileloc is nullable, but DAGResponse typed it as fileloc: str. So a Dag that has runs but a null fileloc (for example one run through dag.test() or the system-test harness) made GET /dags/{id} and /dags/{id}/details fail validation and return 500, leaving the detail page stuck loading.

This makes fileloc nullable so those endpoints return 200 and the page renders the Dag with its runs. The OpenAPI spec, UI client, and airflow-ctl datamodels are regenerated to match, and the UI handles a missing file location.

closes: #69035

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:airflow-ctl area:API Airflow's REST/HTTP API area:UI Related to UI/UX. For Frontend Developers. backport-to-airflow-ctl/v0-1-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UI: DAG detail page 500s / infinite load for DAGs with run history but no parsed definition (e.g. created by dag.test()/system tests)

1 participant