You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "vatsrahul1001 (via GitHub)" <gi...@apache.org> on 2026/01/28 12:30:56 UTC
[PR] Add guardrail to handle DAG deserialization errors in scheduler [airflow]
vatsrahul1001 opened a new pull request, #61162:
URL: https://github.com/apache/airflow/pull/61162
Wraps _get_current_dag() calls in _create_dag_runs and _create_dag_runs_asset_triggered with try/except. If deserialization fails, the scheduler logs the error and continues to the next DAG instead of crashing.
* Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment: `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add guardrail to handle DAG deserialization errors in scheduler [airflow]
Posted by "vatsrahul1001 (via GitHub)" <gi...@apache.org>.
vatsrahul1001 commented on PR #61162:
URL: https://github.com/apache/airflow/pull/61162#issuecomment-3817120770
> Better than crashing the scheduler hard, though I wonder if will this continue to try and get it very loop around the scheduler leading to log spam and other knock on issues? Since the dag that is failing will still get returned in the DagModel.dags_needing_dagruns list (Ditto for anything asset related too?)
>
> Not sure how best to address this...
Maybe modifying dags_needing_dagruns query to exclude DAGs with certain warning types?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add guardrail to handle DAG deserialization errors in scheduler [airflow]
Posted by "vatsrahul1001 (via GitHub)" <gi...@apache.org>.
vatsrahul1001 merged PR #61162:
URL: https://github.com/apache/airflow/pull/61162
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org