# Concurrency in v17.1

**URL:** <https://forum.ansible.com/t/concurrency-in-v17-1/3305>\
**Category:** Get Help\
**Tags:** awx\
**Created:** [January 14, 2024, 10:55am UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305 "2024-01-14T10:55:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![flodo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flodo/32/1989_2.png) [@flodo](https://forum.ansible.com/u/flodo)\
**Post date:** [January 14, 2024, 10:55am UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305/1 "2024-01-14T10:55:00Z")

</div>

I’ve read that prior Ansible Tower 3.0 concurrent jobs from the same template blocked each other (last section [here](https://docs.ansible.com/ansible-tower/3.2.7/html/userguide/jobs.html)).

I think this is what happens in my setup as well, in my AWX 17.1 setup only one job runs at a time (multiple jobs from the same template), I am wondering if that is due to such a blocking or due to capacity problems - not sure since I hadn’t found out when that changed in AWX.

=\> I ask myself: will upgrading the server capacity help or is the problem the outdated AWX version and therefore the blockage.

I already had a look in GitHub but without success so far. Can someone help me, please?

**EDIT** :  
found the following in the logs for a second job of the same template

```Jan
Jan 14 11:49:55 awx d77fd34d2820[10174]: 2024-01-14 11:49:55,869 DEBUG awx.main.scheduler No instance available in group tower to run job job 114568 (pending) w/ capacity requirement 6
Jan 14 11:49:55 awx d77fd34d2820[10174]: 2024-01-14 11:49:55,871 DEBUG awx.main.scheduler job 114568 (pending) couldn't be scheduled on graph, waiting for next cycle
Jan 14 11:49:55 awx d77fd34d2820[10174]: 2024-01-14 11:49:55,872 DEBUG awx.main.scheduler Finishing Scheduler

```

So seem like it is a capacity issue then, right?

---

<div class="post-metadata">

**Author:** ![djyasin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/djyasin/32/114_2.png) [@djyasin](https://forum.ansible.com/u/djyasin)\
**Post date:** [January 17, 2024, 8:03pm UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305/2 "2024-01-17T20:03:12Z")

</div>

Hello @flodo  
Do you have Concurrent Jobs selected? Here is a screenshot of where that lives:

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/7/7f7d213b045cf467c6551520a78456aafa0eaf54.png)

---

<div class="post-metadata">

**Author:** ![flodo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flodo/32/1989_2.png) [@flodo](https://forum.ansible.com/u/flodo)\
**Post date:** [January 17, 2024, 8:26pm UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305/3 "2024-01-17T20:26:16Z")

</div>

Heya, sure thing. Have selected that

---

<div class="post-metadata">

**Author:** ![fosterseth](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/fosterseth/32/101_2.png) [@fosterseth](https://forum.ansible.com/u/fosterseth)\
**Post date:** [January 19, 2024, 6:34pm UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305/4 "2024-01-19T18:34:27Z")

</div>

to clarify, you are on awx 17? If so we highly recommend upgrading to latest AWX, we’ve made a load of improvements around job capacity / concurrency.

Let us know if you have questions about upgrading to newer version

Seth

---

<div class="post-metadata">

**Author:** ![flodo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flodo/32/1989_2.png) [@flodo](https://forum.ansible.com/u/flodo)\
**Post date:** [February 4, 2024, 2:37pm UTC](https://forum.ansible.com/t/concurrency-in-v17-1/3305/5 "2024-02-04T14:37:11Z")

</div>

That’s correct, mainly because I have no experience with kubernetes so far. So it is hard for me to do the upgrade.