wilsonhooi86 commented on issue #62353: URL: https://github.com/apache/airflow/issues/62353#issuecomment-3970281482
> > > Ｉwill take a look. Thanks for sharing! > > > > > > Thank you so much, [@henry3260](https://github.com/henry3260) . This feature will be very helpful for our current use cases. Really appreciate your support. > > Can I ask Did the first run fail before the XCom push? Hi @henry3260 , I not too sure on that. It was hard for me to test by having an internal failure that caused the GlueJobOperator's task to fail on its own. So, to simulate task's retry, what I did was below steps: 1. Manual run the dag with GlueJobOperator 2. When the GlueJobOperator's task was running for few minutes, I mark the task as `FAILED` 3. After that, I click on the failed GlueJobOperator's task and clear the task and it went into retry mode as screenshot above. But somehow during the retry mode, it creates a new Glue Job ID to run. -- 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]
