roydobbe opened a new issue, #64828: URL: https://github.com/apache/airflow/issues/64828
### Under which category would you file this issue? Providers ### Apache Airflow version 2.11.1 ### What happened and how to reproduce it? ## Repair run: Whenever a repair run is triggered, the job parameters need to be passed to the api endpoint for it to register the params for the tasks again. I tried replicating the operator logic locally, but only when i explicitly passed the job parameters to the repair endpoint, I saw the parameters for the task it was repairing resolved. Currently the operator only updates the job parameters as an intermediate step before triggering the repair endpoint, but doesn't pass it along in the repair_json object. ## Idempotency token This may be expected behavior but, when we retry an airflow task with an idempotency token, it results in a successful state, even if the task its retrying has failed initially. We would expect it to trigger a repair run if repair run is true, else we would expect a failed state. ### What you think should happen instead? _No response_ ### Operating System _No response_ ### Deployment Astronomer ### Apache Airflow Provider(s) databricks ### Versions of Apache Airflow Providers databricks - 7.12 ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [x] 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]
