Task was marked as running but was not present in the job queue, so it has been marked as failed.

Archives AWX Project
1

On AWX 21.4.0 I am running one job for 24x7. out of almost 250 job runs 10 jobs are getting this error: “Task was marked as running but was not present in the job queue, so it has been marked as failed.”

though the job gets completed. playbook runs completely. but in job status it show failed.

please suggest.

thanks,
Jagruti

2

Hi Team,
Any. update on this error: “Task was marked as running but was not present in the job queue, so it has been marked as failed.”

3

do you see any other errors in the awx-task container related to the failed job (grep for job id)?

was this the only job running at the time it failed? or was the system busy running other stuff too?

4

Hi
90% of the time this job runs 25x7 on demand basis.
Per day approximately 600 jobs runs with same workflow.

So there is sure possibility that parallel jobs might be running at the time of failure and that’s the nature of
This wax environment to run parallel jobs right ?

Correct me if I’m wrong.
Thanks
Jagruti Belani

5

Hi. we have made recent improvements around this area of code. Do you mind upgrading to 21.7.0 and letting us know if you still have these failures? that would be a very useful datapoint to have and would help us prioritize the issue

AWX Team

6

Hi Team,
is there any documentation link for the changes for “Task was marked as running but was not present in the job queue, so it has been marked as failed.” issue the job gets completed successfully but appears in job details as failed.

Please share the information. Just upgrdaiing the version for small small things is not feasible for us. we have a large AWX environment setup.