seosuho opened a new issue, #50938:
URL: https://github.com/apache/airflow/issues/50938

   ### Official Helm Chart version
   
   1.13.1
   
   ### Apache Airflow version
   
   v2.10.3
   
   ### Kubernetes Version
   
   v1.26.4
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   We observed that the GET /dags REST API endpoint returns "is_active": true 
for DAGs that are paused in the Airflow UI.
   
   For example, we have DAGs like airflow_db_clean and airflow that are marked 
as paused in the Airflow UI, but the REST API still returns "is_active": true. 
This behavior is consistent across all DAGs that are paused.
   
   ### What you think should happen instead
   
   The is_active field in the REST API should reflect the same DAG state shown 
in the Airflow UI. If a DAG is paused in the UI, its is_active field should be 
false (or a different field clearly indicating its current scheduling status 
should be provided).
   
   ### How to reproduce
   
   step1) Navigate to Airflow UI → DAGs tab.
   step2) Pause a DAG such as airflow_db_clean.
   step3) Go to Docs → REST API Reference (Swagger UI).
   step4) Execute the GET /dags API.
   step5) Observe that the "is_active" field for paused DAGs is still true.
   
   sample api resoponse => 
   
   {
     "dag_id": "airflow_db_clean",
     "is_active": true,
     "is_paused": true
   }
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to