The Log URL (ti.log_url) from the triggered retry email doesn't redirect to the Logs when clicked but instead shows 'No XCom' as the error in the Airflow UI. The Logs are shown when a time in future is selected as the base_date in the UI.
Before changing the base_date in the UI,
After adding 1 second to the base_date in UI,
What you think should happen instead?
I think the issue might be due to milli seconds getting truncated which causes the difference between the execution datetime (untruncated) and the execution datetime rendered - base_date (truncated) in the ti.log_url
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.10.1
What happened?
The Log URL (
ti.log_url
) from the triggered retry email doesn't redirect to the Logs when clicked but instead shows 'No XCom' as the error in the Airflow UI. The Logs are shown when a time in future is selected as thebase_date
in the UI.Before changing the base_date in the UI,
After adding 1 second to the base_date in UI,
What you think should happen instead?
I think the issue might be due to milli seconds getting truncated which causes the difference between the execution datetime (untruncated) and the execution datetime rendered -
base_date
(truncated) in theti.log_url
How to reproduce
Here is the DAG to reproduce the issue,
Click the Log
Link
from the email triggered by the DAGOperating System
Linux
Versions of Apache Airflow Providers
No response
Deployment
Amazon (AWS) MWAA
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct