harshith-bolar-rapido commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-258729
For now the workaround is to go into `task_instance` and make
`try_number=max_tries` and clear the task in UI. We are running a mix of celery
and Kubernetes executors
harshith-bolar-rapido commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-066452
@Karpisek No, it still happens randomly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Karpisek commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-2117614006
@harshith-bolar-rapido hi, have you been able to resolve the issue? (we are
facing it too on AF version 2.5.3)
--
This is an automated message from the Apache Git Service.
To re
harshith-bolar-rapido commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-1947761572
Seeing this in airflow 2.5.3
--
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
github-actions[bot] closed issue #20047: ERROR: could not queue task
TaskInstanceKey
URL: https://github.com/apache/airflow/issues/20047
--
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
github-actions[bot] commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-1871796066
This issue has been closed because it has not received response from the
issue author.
--
This is an automated message from the Apache Git Service.
To respond to the
github-actions[bot] commented on issue #20047:
URL: https://github.com/apache/airflow/issues/20047#issuecomment-1829224839
This issue has been automatically marked as stale because it has been open
for 365 days without any activity. There has been several Airflow releases
since last activit
