Buttons can help you keep an unattended installation healthy by surfacing which connection needs attention, why, and giving you a one-click way to hand support everything they need. This page explains how to read a connection's status and logs, when Buttons restarts a connection automatically, and what to do when a connection needs your attention.
Each connection runs as its own process. Buttons watches its CPU and memory use and can restart it automatically if either stays too high for too long: this protects the rest of your system from one misbehaving connection, but it is not a general safety net. A connection that keeps failing for another reason, such as a wrong address or bad credentials, restarts every time it fails and keeps trying indefinitely. Buttons does not detect that pattern as a distinct problem or stop retrying on its own, so a failing connection needs you to notice it and fix the underlying cause.
Two places tell you what is happening:
The connection's status banner, such as Connected, Connecting, Disconnected, or Bad configuration.
Its Connection Logs, filterable by level (Error, Warn, Info, Verbose, Debug).
Do not assume a quiet log means a healthy connection. Some failure modes only produce Debug-level messages, so a connection can be failing continuously while its Error and Warn filters show nothing.
A connection has been running for weeks without incident. Its CPU or memory use has been trending upward, and it has now restarted on its own.
Open Connect → Connection and select the connection.
Look at the CPU and Memory badges at the top of its detail view.
Open the Monitoring tab. Under Resource thresholds, CPU thresholds and Memory thresholds each show a Warning and a Restart level; Buttons restarts the connection once its one-minute average usage exceeds the restart level.
Decide what the restart tells you:
If this connection is legitimately resource-heavy for what it does, raise its thresholds so routine use does not restart it as often.
If the trend looks like a leak or a stuck loop inside the connection itself, treat the restart as a symptom, not a fix: check for a newer module version or contact support with the connection's logs.
Under Logging on the same tab, Keep historical log data ("Save connection log data for inclusion in support packages") is off by default. Turn it on for a connection you expect to need to hand to support later.
A connection has been failing to reach its target for some time without anyone noticing, because nothing about it looked urgent.
Open Connect → Connection and check each connection's status in the list, not just whether it appears Connected.
Select a connection whose status stays on Connecting rather than settling into Connected or Disconnected. That pattern (never resolving either way) usually means Buttons is retrying the same failure repeatedly.
Open Connection Logs and select All levels. A connection stuck like this can log only Debug-level reconnect entries, once per attempt, with nothing at Error or Warn.
Fix the cause directly: confirm the target address, credentials, and network path outside Buttons, then correct the connection's configuration. Restarting the connection does not help if the underlying cause is still there; it will simply resume retrying.
