# Failover Question

**URL:** <https://forum.inductiveautomation.com/t/failover-question/103952>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 20, 2025, 2:22pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952 "2025-03-20T14:22:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\
**Post date:** [March 20, 2025, 2:22pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/1 "2025-03-20T14:22:41Z")

</div>

I have not done a ton of failover stuff so I am trying to verify if you can failover to a full-blown gateway.

If I have Gateway A and Gateway B and B goes down, can I failover my clients to the A side if there is a project of the same name even though it is not redundant. Instead, I have it setup as Independent.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 20, 2025, 2:40pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/2 "2025-03-20T14:40:39Z")

</div>

Local client fallback is essentially a hard cutover to whatever the local gateway **designates** as the fallback project:

> **[Local Client Fallback | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/vision/local-client-fallback#enable-fallback)**
>
> Ignition Clients are fully dependent on being able to communicate with a Gateway. If Gateway communication is lost, the Client suspends operation while it attempts to reconnect with the Gateway. This can be a problem when you need the Client to...

There's no attempt to transfer client state, and no need for the project names or anything to line up. It's just a more-or-less "seamless" \[1\] switch from running one project from one gateway to running a different project from the local gateway (akin to a `system.util.retarget` operation).

* * *

1. how seamless it will be depends on how closely aligned the two versions are; switching versions may require a JVM restart which adds time, but it will still be automatic

---

<div class="post-metadata">

**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\
**Post date:** [March 20, 2025, 2:42pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/3 "2025-03-20T14:42:53Z")

</div>

Is there a way to achieve this for Perspective as well?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 20, 2025, 2:46pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/4 "2025-03-20T14:46:09Z")

</div>

In workstation, yes:

> **[Perspective Workstation | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/launchers-and-workstation/perspective-workstation#advanced---fallback-redirect-settings)**
>
> The Perspective Workstation is a single application that acts as both a launcher, and desktop “wrapper” for Perspective Sessions. Perspective Workstation allows you to run your Perspective applications as first class desktop applications designed...

Not for browser launched sessions. I'm not sure about the mobile app...

---

<div class="post-metadata">

**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\
**Post date:** [March 20, 2025, 2:52pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/5 "2025-03-20T14:52:10Z")

</div>

For a web browser I theory you could detect that the gateway is unreachable and then redirect to a new URL of your "failover". It would just not be quite seamless.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 20, 2025, 3:10pm UTC](https://forum.inductiveautomation.com/t/failover-question/103952/6 "2025-03-20T15:10:52Z")

</div>

_You_ could, using some kind of loadbalancing strategy or some other service "in front of" Ignition. _We_ cannot, because if you point at the gateway's IP (while it's down), your web browser is just not going to find anything. Once a session is launched, we do cache some info and attempt to seamlessly switch over to the _backup_ node, for redundancy failover, but we don't have any analogue for falling back to arbitrary different gateways. And we have no interest in maintaining/providing a load balancer or reverse proxy first party, because that's well tread ground that you can easily find free solutions for.
