# 8.3 version upgrade reverted UDT Tags to Default Values

**URL:** <https://forum.inductiveautomation.com/t/8-3-version-upgrade-reverted-udt-tags-to-default-values/117546>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [October 20, 2026, 5:55pm UTC](https://forum.inductiveautomation.com/t/8-3-version-upgrade-reverted-udt-tags-to-default-values/117546 "2026-10-20T17:55:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dominicfabiilli](https://avatars.discourse-cdn.com/v4/letter/d/c6cbf5/32.png) [@dominicfabiilli](https://forum.inductiveautomation.com/u/dominicfabiilli)\
**Post date:** [October 20, 2026, 5:55pm UTC](https://forum.inductiveautomation.com/t/8-3-version-upgrade-reverted-udt-tags-to-default-values/117546/1 "2026-10-20T17:55:39Z")

</div>

My customer has multiple sites with redundant scale out architecture

(Frontend server pair, Backend server pair, all tags live on Backend, with frontend remote providers).

We just upgraded 2 sites from 8.3.7 to 8.3.10.

Here is the upgrade procedure:

1. Frontend force failover
2. Upgrade Frontend Primary (which takes back control)
3. Upgrade Frontend Secondary
4. Backend force failover
5. Upgrade Backend Primary (which takes back control)
6. Upgrade Backend Secondary

It seems like some configuration tags and UDTs reverted to their default values.

- config tags (Memory) that were recently FALSE were now set to default-TRUE
- UDT strings (Memory) with parameter info were set to default-BLANK

On our next upgrade, we will try to see if the incident occurs specifically on a forced failover or the actual version upgrade.

Has anyone else seen this?

Any ideas on how to prevent this for future upgrades?

Thanks