# Help wanted with AWX / AKS problem

**URL:** <https://forum.ansible.com/t/help-wanted-with-awx-aks-problem/46564>\
**Category:** Get Help\
**Tags:** awx\
**Created:** [October 30, 2026, 12:30pm UTC](https://forum.ansible.com/t/help-wanted-with-awx-aks-problem/46564 "2026-10-30T12:30:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ildjarn](https://avatars.discourse-cdn.com/v4/letter/i/8491ac/32.png) [@ildjarn](https://forum.ansible.com/u/ildjarn)\
**Post date:** [October 30, 2026, 12:30pm UTC](https://forum.ansible.com/t/help-wanted-with-awx-aks-problem/46564/1 "2026-10-30T12:30:08Z")

</div>

I hope someone can help me.

I upgraded the node pool for our AKS cluster from 2 Standard\_D4s\_v3 servers to 2 Standard D4as\_v7 servers.  
The nodes are almost picking their nose because they have very little to do, but since the upgrade I get the following error a few times now:  
`Task was marked as running but was not present in the job queue, so it has been marked as failed.`  
I can’t imagine that the change from D4s to D4as has _that_ much impact on the performance of AWX, and CPU/Memory of the nodes never reach very high levels (highest memory usage of the node I’ve seen was around 60%).

I found [Task was marked as running in Tower but was not present in the job queue, so it has been marked as failed · Issue #9594 · ansible/awx · GitHub](https://github.com/ansible/awx/issues/9594) but that issue is still open.

Anyone has a clue why a D4s\_v3 wouldn’t show this behaviour and a D4as\_v7 would?