# Create a deploment incorrect targeted device list

**URL:** <https://hub.mender.io/t/create-a-deploment-incorrect-targeted-device-list/3382>\
**Category:** General Discussions\
**Tags:** integration\
**Created:** [March 16, 2021, 6:17pm UTC](https://hub.mender.io/t/create-a-deploment-incorrect-targeted-device-list/3382 "2021-03-16T18:17:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [March 16, 2021, 6:17pm UTC](https://hub.mender.io/t/create-a-deploment-incorrect-targeted-device-list/3382/1 "2021-03-16T18:17:55Z")

</div>

I’m seeing a problem on self hosted mender server 2.4.1 when a create a deployment for a release.  
When i select the device group to deploy to it always says 1 device will be targeted. If i click the X next to the selected entry and select the same group again i then get the expected number of devices.

Is this something thats fixed in newer versions of server?

 ![mender-deploy-1st-click](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/7/72756d6fa5efe4a22ad36f552ae4ad3df7e8a119.png)

 ![mender-deploy-2nd-click](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/a/ac27755e6b72684482ddb9b682613dcb96f460aa.png)

---

<div class="post-metadata">

**Author:** ![mzedel](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mzedel/32/261_2.png) [@mzedel](https://hub.mender.io/u/mzedel)\
**Post date:** [March 19, 2021, 4:11pm UTC](https://hub.mender.io/t/create-a-deploment-incorrect-targeted-device-list/3382/2 "2021-03-19T16:11:36Z")

</div>

What you are seeing is the delay the frontend needs to determine the device list for the group. On initial UI opening, groups are only initialised with a single device (thus the 1 device targeted). Once the _Devices/Device Groups_ tab was opened or the group was selected, the group info is kept in the ui state though.  
Unfortunately the handoff of the device list resolution for fixed groups depends on changes in backend that were too large to backport to 2.4 and only released in 2.6.