Repository navigation
404 not found for operators when navigating versions post 2.10.4. #54255
Copy link
Copy link
Closed
Labels
area:providerskind:bugThis is a clearly a bugThis is a clearly a bugkind:documentationneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
Activity
- addedkind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
on Aug 8, 2025 Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Hi @potiuk
As per release notes
SubDag support has been removed entirely, including the SubDagOperator, related CLI and API interfaces. TaskGroups are now the recommended alternative for nested DAG structures.How shall we handle the redirects here for SubDagOperator ?
Hi @potiuk
As per release notes
SubDag support has been removed entirely, including the SubDagOperator, related CLI and API interfaces. TaskGroups are now the recommended alternative for nested DAG structures.How shall we handle the redirects here for SubDagOperator ?
Redirects it to the release notes :) ?
- added a commit that references this issue
on Aug 13, 2025 - added a commit that references this issue
on Aug 13, 2025 - added a commit that references this issue
on Aug 13, 2025 - added a commit that references this issue
on Sep 3, 2025
Metadata
Metadata
Assignees
Labels
area:providerskind:bugThis is a clearly a bugThis is a clearly a bugkind:documentationneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Apache Airflow Provider(s)
standard
Versions of Apache Airflow Providers
No response
Apache Airflow version
main
Operating System
linux
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
What happened
Encountered 404 not found error message when I click on operator with v2.10.4+
What you think should happen instead
Redirects should happen to apache-airflow-providers-standard operators rather than 404 not found error message to user
How to reproduce
operators and hooks airflowon chrome.Click on any of the operator.
Problematic links are mentioned below -
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/bash/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/branch/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/email/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/generic_transfer/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/latest_only/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/python/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/subdag/index.html
https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/trigger_dagrun/index.html
Note - for empty and datetime operators fix has been already provided as part of #53965
Anything else
No response
Are you willing to submit PR?
Code of Conduct