Skip to content

Retry TriggerDagRunOperator when the triggered DagRun fails#65390

Open
SamWheating wants to merge 3 commits intoapache:mainfrom
SamWheating:sw-fix-triggerdagrunoperator-retries
Open

Retry TriggerDagRunOperator when the triggered DagRun fails#65390
SamWheating wants to merge 3 commits intoapache:mainfrom
SamWheating:sw-fix-triggerdagrunoperator-retries

Conversation

@SamWheating
Copy link
Copy Markdown
Contributor

@SamWheating SamWheating commented Apr 16, 2026

closes: #62970

Picking up from: #62973 since this issue is causing some noise in a few of our pipelines, and I want to make sure this gets sorted out.

The previous PR was mostly good to go, I just made a few minor changes:

  • In the case that a conflicting DAGRun exists, we should never be retrying (since this will just re-fail)
  • Fixed variable assignment which was confusing mypy

I have reproduced the original issue in breeze (with LocalExecutor) and verified that this fix works. I will run the reproduction on Breeze with the KubernetesExecutor tomorrow and verify that it works there too.


Was generative AI tooling used to co-author this PR?
  • Yes, kbohra used cursor tab completion in the original PR

@SamWheating SamWheating changed the title Sw fix triggerdagrunoperator retries Retry TriggerDagRunOperator when the triggered DagRun fails Apr 16, 2026
@SamWheating SamWheating force-pushed the sw-fix-triggerdagrunoperator-retries branch from 9102bfa to 8e66045 Compare April 17, 2026 08:48
@SamWheating SamWheating marked this pull request as ready for review April 17, 2026 08:48
@SamWheating
Copy link
Copy Markdown
Contributor Author

SamWheating commented Apr 17, 2026

cc @kbohra - I hope its ok that I picked up your previous draft PR. I pulled in your original commits to give credit where its due.

Take a look and let me know what you think 😄

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TriggerDagRunOperator does not retry when triggered DAGs time out with Kubernetes Executor

2 participants