karenbraganz commented on issue #47781:
URL: https://github.com/apache/airflow/issues/47781#issuecomment-2725910325
I tested this out and am also seeing the error you mentioned. The task is
added to queue but fails before it can start running.
```
[2025-03-14T22:25:46.102+0000] {scheduler_job_runner.py:692} INFO - Sending
TaskInstanceKey(dag_id='sla_breach_warning', task_id='get_opened_ticket_id',
run_id='manual__2025-03-14T22:25:45.018635+00:00', try_number=1, map_index=-1)
to CeleryExecutor with priority 17 and queue default
[2025-03-14T22:25:46.102+0000] {base_executor.py:169} INFO - Adding to
queue: ['airflow', 'tasks', 'run', 'sla_breach_warning',
'get_opened_ticket_id', 'manual__2025-03-14T22:25:45.018635+00:00', '--local',
'--subdir', 'DAGS_FOLDER/sla_breach_warning_dag.py']
[2025-03-14T22:25:46.134+0000] {celery_executor.py:312} ERROR - Error
sending Celery task: execute_command() takes 1 positional argument but 9 were
given
Celery Task ID: TaskInstanceKey(dag_id='sla_breach_warning',
task_id='get_opened_ticket_id',
run_id='manual__2025-03-14T22:25:45.018635+00:00', try_number=1, map_index=-1)
Traceback (most recent call last):
File
"/usr/local/lib/python3.12/site-packages/airflow/providers/celery/executors/celery_executor_utils.py",
line 270, in send_task_to_executor
result = task_to_run.apply_async(args=args, queue=queue)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/celery/app/task.py", line
559, in apply_async
check_arguments(*(args or ()), **(kwargs or {}))
TypeError: execute_command() takes 1 positional argument but 9 were given
[2025-03-14T22:25:46.134+0000] {scheduler_job_runner.py:776} INFO - Received
executor event with state failed for task instance
TaskInstanceKey(dag_id='sla_breach_warning', task_id='get_opened_ticket_id',
run_id='manual__2025-03-14T22:25:45.018635+00:00', try_number=1, map_index=-1)
```
--
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]
