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

   ### Apache Airflow version
   
   3.1.3
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Since my last upgrade (3.1.1 -> 3.1.3) I have an issue with my retry 
strategy.
   
   I have a DAG with : 
   - default_args: { retries: 3 }
   - a task with custom retry parameter: @task(retries=0)
   
   The task is still retried when DAG fails.
   
   Very simplified version of my dag is
   
   ```python
   
       @dag(
           default_args={
               retries: 3
           }
       )
       def my_dag():
           @task_group(group_id="group")
           def my_task_group(seller: Dict) -> str:
   
               @task(retries=0)
               def my_task(job_id: str) -> None:
                   ### some code
   ```
   
   Yet I see multiple retries on this task
   
   <img width="478" height="125" alt="Image" 
src="https://github.com/user-attachments/assets/49fe7aa2-5340-40a2-88ba-957e524d79d7";
 />
   
   I checked and I never had this issue with 3.1.1.
   
   Maybe it's related to https://github.com/apache/airflow/pull/57853
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   See DAG example
   
   ### Operating System
   
   macos
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### 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