# Project saves, affecting gateway events or tag browser scripts **URL:** \ **Category:** Ignition\ **Created:** [July 3, 2025, 4:21pm UTC](https://forum.inductiveautomation.com/t/project-saves-affecting-gateway-events-or-tag-browser-scripts/108114 "2025-07-03T16:21:08Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Andrew\_Lin](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@Andrew\_Lin](https://forum.inductiveautomation.com/u/Andrew_Lin)\ **Post date:** [July 3, 2025, 4:21pm UTC](https://forum.inductiveautomation.com/t/project-saves-affecting-gateway-events-or-tag-browser-scripts/108114/1 "2025-07-03T16:21:08Z")
So, the issue I have is whenever I save my project after making changes, all the gateway tag change scripts will be fired off checking conditions again... (something I don't want happening). So far, I have scripts in the tag browser... When I save a project will all the scripts in the tag browser execute or does it not because it is separate from the gateway. I would assume we can use the `initialChange` parameter as a way to resolve this if it does execute. As for the gateway tag change scripts I always see them fire off... I don't have access to the `inititalChange` parameter but I would assume we can use the `event.currentValue.value != event.previousValue.value`? But sometimes I notice I won't have a `previousValue` to even extract the value from... Is there a safe and guarantee way to prevent these scripts from firing off whenever a project is saved? This is for both gateway tag change scripts and tag browser tag change scripts. ---
**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:** [July 3, 2025, 4:28pm UTC](https://forum.inductiveautomation.com/t/project-saves-affecting-gateway-events-or-tag-browser-scripts/108114/2 "2025-07-03T16:28:18Z")
Both types signal `initialChange`, and that is its purpose. `previousValue` doesn't exist when `initialChange` is true. Consider using multiple projects, perhaps with inheritance, to keep your tag changes from firing when you are editing user interfaces.