# Prevent Designer Re-Load on Module Update

**URL:** <https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514>\
**Category:** Module Development\
**Tags:** sdk, ignition81\
**Created:** [May 21, 2025, 4:13pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514 "2025-05-21T16:13:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cody.tamaki](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cody.tamaki](https://forum.inductiveautomation.com/u/cody.tamaki)\
**Post date:** [May 21, 2025, 4:13pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514/1 "2025-05-21T16:13:26Z")

</div>

Is there any way to prevent a designer for forcibly restarting if we push a module updates? I'd rather assume the risk of having an out of date designer if I'm only working on updates to the gateway scope...

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 21, 2025, 4:16pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514/2 "2025-05-21T16:16:31Z")

</div>

No, the designer is not equipped to determine what has changed and only restart if "safe".

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 21, 2025, 5:03pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514/3 "2025-05-21T17:03:04Z")

</div>

If your designer is launched with an explicit version flag of `dev` (`-Dscadarail.version=dev` in 8.1, `-Dignition.version=dev` in 8.3) the designer will ignore its typical module version/update related checks. Just be very aware of the risks of **weird** things happening.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 21, 2025, 5:21pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514/4 "2025-05-21T17:21:25Z")

</div>

> [@paul-griffith](#):
>
> an explicit version flag of `dev`

Hmmm. I may start using this.

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [May 21, 2025, 5:59pm UTC](https://forum.inductiveautomation.com/t/prevent-designer-re-load-on-module-update/106514/5 "2025-05-21T17:59:50Z")

</div>

Ooh, this will be nice when working on Perspective components.