Handle Controller service unavailable
Use a calm staff checklist when the Controller cannot reach local branch services or live operational data.
Staff can check the practical causes first and escalate with useful context instead of changing branch setup blindly.
Before you start
- Know which computer or service hosts the local branch Controller service.
- Staff can identify whether the problem is one browser, one PC, or the branch service.
- Owners have defined who may restart the service or host machine.
Check the browser and device
Sometimes the issue is only the staff browser or workstation. Check that before escalating.
- Refresh the Controller page once.
- Check whether another staff device can open the Controller.
- Confirm the staff PC still has branch network access.
Check the local service
If multiple staff devices cannot reach local operation, check the service host and branch network.
- Confirm the host machine is powered on and connected.
- Check whether local branch services were restarted or updated.
- Restart only through the approved branch process.
Escalate with context
Good context speeds up support. Staff should report what changed and which devices are affected.
- Record the time the issue started.
- List whether Agent PCs, displays, and staff browser are affected.
- Mention recent updates, power events, or network changes.
Verify it worked
- Staff can reproduce whether the issue affects one browser or the branch service.
- The local service host is checked before changing setup.
- Support escalation includes time, affected devices, and recent changes.
Troubleshooting
Only one staff browser shows unavailable.
Refresh, sign in again if needed, and check that workstation network before restarting branch services.
All staff devices show unavailable.
Check the local service host, branch router, power, and approved restart process.