# Redundancy : trigger failover by scripting

**URL:** <https://forum.inductiveautomation.com/t/redundancy-trigger-failover-by-scripting/63137>\
**Category:** Ignition\
**Created:** [August 18, 2022, 7:20am UTC](https://forum.inductiveautomation.com/t/redundancy-trigger-failover-by-scripting/63137 "2022-08-18T07:20:14Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [August 18, 2022, 3:32pm UTC](https://forum.inductiveautomation.com/t/redundancy-trigger-failover-by-scripting/63137/10 "2022-08-18T15:32:36Z")

</div>

We don’t currently have a supported mechanism for this, but the most basic action can be achieved with:

```python
from com.inductiveautomation.ignition.gateway.redundancy.types import ActivityLevel
from com.inductiveautomation.ignition.gateway import IgnitionGateway

redundancy_manager = IgnitionGateway.get().getRedundancyManager()
redundancy_manager.requestPeerActivityLevel(ActivityLevel.Active)

```

The above effectively requests the peer to become Active. There are some _System_ tags available for discovering the current state of redundancy (that might be handy for deciding when to invoke the above).

---

_[View the full topic](https://forum.inductiveautomation.com/t/redundancy-trigger-failover-by-scripting/63137)._