# Targeted deploy triggering a new version notification in another app

**URL:** <https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483>\
**Category:** Bug reports\
**Created:** [October 27, 2026, 9:23am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483 "2026-10-27T09:23:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/erik/32/78_2.png) [@Erik](https://community.appfarm.io/u/Erik)\
**Post date:** [October 27, 2026, 9:23am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483/1 "2026-10-27T09:23:43Z")

</div>

Hi! We’re experiencing an issue where targeted deploy doesn’t seem to work as expected.

We recently deployed a minimal change, an update to a single action in one application, using targeted deploy. However, users in another application were also notified that a new version of their app was available and were forced to reload the application.

We expected the deployment to only affect the selected application.

---

<div class="post-metadata">

**Author:** ![daniel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/daniel/32/2882_2.png) [@daniel](https://community.appfarm.io/u/daniel)\
**Post date:** [October 27, 2026, 11:04am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483/2 "2026-10-27T11:04:51Z")

</div>

We have experienced the same issue several times.

---

<div class="post-metadata">

**Author:** ![emma](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/emma/32/1649_2.png) [@emma](https://community.appfarm.io/u/emma)\
**Post date:** [October 28, 2026, 8:01am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483/3 "2026-10-28T08:01:49Z")

</div>

Hi,

Thank you for letting us know!

Which Create version are you on @Erik and @daniel ?

And do you remember when this started to happen?

- Emma

---

<div class="post-metadata">

**Author:** ![Erik](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/erik/32/78_2.png) [@Erik](https://community.appfarm.io/u/Erik)\
**Post date:** [October 28, 2026, 8:15am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483/4 "2026-10-28T08:15:16Z")

</div>

Hi Emma,

We’re on Create version 164-0-21. My impression is that this has been an issue for a long time, but I can’t pinpoint when we first noticed it.

---

<div class="post-metadata">

**Author:** ![daniel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/daniel/32/2882_2.png) [@daniel](https://community.appfarm.io/u/daniel)\
**Post date:** [October 28, 2026, 8:34am UTC](https://community.appfarm.io/t/targeted-deploy-triggering-a-new-version-notification-in-another-app/2483/5 "2026-10-28T08:34:21Z")

</div>

My experience is, we do not in general rely on targeted deploy not affecting other applications because of repeated feedback from users.