Gateway restored—why is the Vision Client still on fallback?
The central Gateway is back, but the Vision Client is still on local fallback. Is the server still down?
Start with the symptom
The central Gateway is back, but the Vision Client is still on local fallback. Is the server still down?
What the documentation establishes
Local Vision Client Fallback can retarget to a local fallback project after the configured wait when the central Gateway is unreachable. The default wait is 60 seconds, but it is configurable.
The reverse path is different: when the main Gateway is available again, Local Vision Client Fallback does not automatically transfer back.
Five checks at a glance
| Scene | Point | Limit |
|---|---|---|
| 1 | Main Gateway restored ≠ automatic return. | Main Gateway recovery is not automatic failback. |
| 2 | Loss of central Gateway → configured wait → local fallback. | The default 60-second wait is configurable. |
| 3 | Main Gateway recovery does not auto-failback. | The asymmetric return behavior is explicitly documented. |
| 4 | Manual return or engineered retarget logic. | Return requires operator action or separately designed and tested retarget logic. |
| 5 | Check Vision, local Gateway/6501 and the published fallback project. | No real plant outage or failover test was performed. |
Do not over-interpret the symptom
Returning requires operator action or separately designed and tested retarget logic. The vendor example script is not an automatically installed feature.
Read-only preflight
- Main Gateway restored ≠ automatic return.
- Loss of central Gateway → configured wait → local fallback.
- Main Gateway recovery does not auto-failback.
- Manual return or engineered retarget logic.
- Check Vision, local Gateway/6501 and the published fallback project.
Evidence limits
Check that this is a Vision Client, the local Gateway and port 6501, and a published fallback project. This is a documentation-based illustration, not a plant outage test.
This article interprets first-party documentation and uses hypothetical diagrams. It does not report a live device, database, customer-data, outage, recovery or performance test.
Watch the short explanation
The public YouTube schedule may be linked here after the provider assigns the native video ID. The article and local video are already self-contained.