# \[BUG ?\] ActivityLevel Tag does not uptade after automatic failback

**URL:** <https://forum.inductiveautomation.com/t/bug-activitylevel-tag-does-not-uptade-after-automatic-failback/75572>\
**Category:** Ignition\
**Created:** [June 27, 2023, 12:14pm UTC](https://forum.inductiveautomation.com/t/bug-activitylevel-tag-does-not-uptade-after-automatic-failback/75572 "2023-06-27T12:14:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deville\_Xavier](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@Deville\_Xavier](https://forum.inductiveautomation.com/u/Deville_Xavier)\
**Post date:** [June 27, 2023, 12:14pm UTC](https://forum.inductiveautomation.com/t/bug-activitylevel-tag-does-not-uptade-after-automatic-failback/75572/1 "2023-06-27T12:14:23Z")

</div>

Version 8.1.28  
I have two redundant gateways GW1 (master) and GW2 (backup)  
In normal mode the activity levels of the gateways are :

- GW1 active
- GW2 warm

If I simulate a loss of connection between the gateways, then the activity levels of the gateways are :

- GW1 active
- GW2 active  
Which is normal.

Then, when the connection between the two gateways comes back, the activity levels of the gateways are :

- GW1 active
- GW2 warm  
Which is normal.

The problem is that the AtivityLevel tag ([System]/Gateway/Redundancy/ActivityLevel) of GW2 is not updated. Its value stays at "active" instead of "warm"

---

<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:** [June 27, 2023, 1:21pm UTC](https://forum.inductiveautomation.com/t/bug-activitylevel-tag-does-not-uptade-after-automatic-failback/75572/2 "2023-06-27T13:21:33Z")

</div>

Sounds like a bug you should report. (This forum is not official support. Open a ticket through IA's support site.)