The agent repeatedly reconnects

Repeated reconnects usually indicate an unstable egress path, an expired working window, a proxy interruption, or an agent process restart.

Example healthy connection log:

TODO_PLACEHOLDER_HERE

Example reconnect/failure log:

TODO_PLACEHOLDER_HERE

Compare the agent and server logs and check:

• heartbeat RTT and timeout messages;
• reconnect count and transport failures in metrics;
• agent process restarts;
• proxy authentication or idle timeout messages;
• TLS certificate validity and clock skew; and
• working-days and killswitch settings.

Try one transport at a time when isolating the problem. Start with the simplest path available, then test the configured fallback transports. Record which transport remains stable before changing the deployment permanently.