# Redundancy Incompatible Platform

**URL:** <https://forum.inductiveautomation.com/t/redundancy-incompatible-platform/61235>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 27, 2022, 11:28am UTC](https://forum.inductiveautomation.com/t/redundancy-incompatible-platform/61235 "2022-06-27T11:28:55Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [July 28, 2022, 9:15pm UTC](https://forum.inductiveautomation.com/t/redundancy-incompatible-platform/61235/16 "2022-07-28T21:15:01Z")

</div>

Sorry for the late response, I’ve been giving these a try lately and just haven’t been able to reproduce what you have been seeing. I think we’d need support eyes on your system to really get a good idea as to what’s going on.  
I will mention that during version mismatch, syncing does not take place as the connection in this instance basically only allows the master to disable the backup. However as of 8.1.19 with change [2393](https://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2022/54636/95), a lot of the duplicate alarm and tag status issues should function a bit better.

---

_[View the full topic](https://forum.inductiveautomation.com/t/redundancy-incompatible-platform/61235)._