eladkal commented on code in PR #30717: URL: https://github.com/apache/airflow/pull/30717#discussion_r1180457724
########## docs/apache-airflow/faq.rst: ########## @@ -441,6 +441,17 @@ If the tasks are not related by dependency, you will need to :ref:`build a custo Airflow UI ^^^^^^^^^^ +Why did my task fail with no logs in the UI? +-------------------------------------------- + +Logs are [typically served when a task reaches a terminal state](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/logging-tasks.html#serving-logs-from-workers). Sometimes, a task's normal lifecycle is disrupted, and the task's +worker is unable to write the task's logs. This typically happens for one of two reasons: + +1. [Zombie Tasks](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#zombie-undead-tasks) +2. Tasks failed after getting stuck in queued (Airflow 2.6.0+) Review Comment: So we should refer to the relevant Airflow setting task_queued_timeout and ask user to check if the threshold chosen is OK for them -- 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]
