Operator hangs in scheduled state
If a task of a DAG-run is not started and hangs in the scheduled state, it could be due to insufficient resources on the host machine to start the operator.
The image above illustrates how this situation would appear in Airflow.
If you wish to run the operator anyway, you can manually decrease the value of ram_mem_mb in the operator’s code using the code-server extension.
Warning
The ram_mem_mb variable defines the amount of memory allocated to this operator.
If it is set too low, the operator might fail since the operation requires more memory than what has been allocated.
After decreasing the value for ram_mem_mb, you need restart the task by following these steps:
Navigate to Airflow and access the graph view of the workflow containing the unstarted task.
Click on the specific task, and in the resulting pop-up window, click on Clear.
This action will restart the selected task as well as all downstream tasks associated with it.”
Alternatively, you can restart the entire job through the Workflow Execution page.