# Master-backup status

**URL:** <https://forum.inductiveautomation.com/t/master-backup-status/110617>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 15, 2025, 7:05am UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617 "2025-09-15T07:05:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jennifer.ang](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@jennifer.ang](https://forum.inductiveautomation.com/u/jennifer.ang)\
**Post date:** [September 15, 2025, 7:05am UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/1 "2025-09-15T07:05:02Z")

</div>

Hi, does anyone know if there's a script available to check the master-backup redundancy status?

---

<div class="post-metadata">

**Author:** ![schenk](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@schenk](https://forum.inductiveautomation.com/u/schenk)\
**Post date:** [September 15, 2025, 9:36am UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/2 "2025-09-15T09:36:44Z")

</div>

There are [system](https://docs.inductiveautomation.com/docs/8.1/platform/tags/types-of-tags/system-tags#redundancy-system-tags) tags available, `[System]Gateway/Redundancy/IsMaster` should give you the status you're looking for.

---

<div class="post-metadata">

**Author:** ![jennifer.ang](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@jennifer.ang](https://forum.inductiveautomation.com/u/jennifer.ang)\
**Post date:** [September 15, 2025, 9:42am UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/3 "2025-09-15T09:42:47Z")

</div>

Thanks for the reply. Found it. Thanks again

---

<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:** [September 15, 2025, 4:54pm UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/4 "2025-09-15T16:54:41Z")

</div>

Be aware that scripts do not run on the inactive gateway in a redundant pair.

---

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [July 12, 2026, 9:14pm UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/5 "2026-07-12T21:14:29Z")

</div>

Sorry to revive this old thread, but I was naively assuming we could use isMaster value change to trigger some event (I am resynching some results that write to a datacenter replicated Postgres server in the event our on prem servers go down). The tag simply goes to an errored state and never runs.

What is the right way to trigger application-level, rather than DB level synchs like this? Using isMaster seemed the most straightforward way to do this, but it is not working the way I thought. I am confused why the tag value would not persist or be syched when switching between master and backup and vice versa.

---

<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:** [July 12, 2026, 9:46pm UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/6 "2026-07-12T21:46:41Z")

</div>

> [@19tb21](#):
>
> trigger some event

Events are scripts. See my comment just above yours.

---

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [July 13, 2026, 2:43pm UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/7 "2026-07-13T14:43:44Z")

</div>

Bad use of the word "event", sorry. I am just trying to fire a tag change script on isMaster. I have no problem running other tag change scripts when it fails over to backup. This one is a ref tag looking at isMaster system tag. It synchs data from an off prem postgres instance with a on prem postgres instance when isMaster transitions from 0 to 1. I have no issues with other tag change scripts, but this one is seemingly not firing. It may just be a misunderstanding of how isMaster works in general, or how it works specifically when using the web server button "Force Failover".

---

<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:** [July 13, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/master-backup-status/110617/8 "2026-07-13T14:59:12Z")

</div>

Perhaps because there is no change? `isMaster` will always be true on the master gateway, and always false on the backup gateway, so they never change. You should be monitoring `isActive` and within that, read and check `isMaster`. (But note that I wouldn't expect to see `isActive` go false, as the script should be disabled by the role.)
