Update Failures You Can See, Answered Questions You Can Reread, and Smoother Reconnects
October 5, 2026 · InfraScout Team
This release brings three smaller changes. Each one removes a moment where InfraScout left you guessing. An agent that fails its update every night now says so on its card. An answered question in chat no longer hides the question you answered. After server maintenance, agents come back gradually instead of all at once.
Agent Cards Say Why an Update Failed
When an agent update fails, InfraScout retries it in the agent's next maintenance windows. Until now, the agent card showed a calm "Update scheduled" while a retry waited. You could have an agent that failed every night and looked perfectly fine. You only found the reason by opening the update history.
The update banner on the agent card now has a Last attempt failed line while a retry is queued. An update that has used up its retries shows its failure in the same place. Where InfraScout recognizes the error, the line tells you what to do next. Typical cases are a host that can't reach the agent download host, a proxy that inspects TLS and breaks the download, a download that failed its checksum, and a new version that can't run on that operating system. Hover over the line to see the agent's raw error. That is also what to send to support.
The most common cause is a firewall or proxy that blocks outbound HTTPS from the host to the release download host. A blocked host doesn't break a running agent, but it does keep the agent on its old version. Network Requirements lists the host and port to allow. Agent Updates explains how retries work.
Agents that were already retrying before this release show the line after their next failed attempt.
Answered Questions Open to the Full Exchange
When the AI pauses to ask you something, the question stays in the conversation after you answer. Until now, it was a single shortened line, cut off in both the question and your answer. Each answered question now opens to the full exchange: the complete question, every option the AI offered with your choice marked, and your answer. If you typed a free-text answer, it wraps onto as many lines as it needs. Questions that were cancelled, timed out or expired show what happened instead.
When the AI asked several questions at once, each one opens on its own. Days later, you can still see exactly what you agreed to and what the AI did next. Chat covers how questions work.
Agents Return Smoothly After Server Maintenance
When the InfraScout server restarts, or a network interruption cuts many agents off at once, all of those agents lose their connection at the same moment. Until now, they reconnected immediately, all at once. On a large fleet, that crowd slowed the reconnect for everyone.
From agent version 0.37.0, an agent that loses a healthy connection waits a short moment before it reconnects. Each agent's wait is different, so the fleet comes back in a steady stream rather than a crowd. A small fleet is back within a few seconds. A very large fleet takes a little longer, without a spike. While an agent waits, its card may show it as offline. That is expected, and it clears as soon as the agent reconnects. Planned handovers during maintenance, and certificate renewals, work as before.
Older agents keep reconnecting as before. They pick up the new behavior with their next update, and the agent and the server can update in either order.
Find Out More
The agent management guide covers the agent cards, and Chat covers the conversation timeline.
Questions or feedback? Reach us at info@infrascout.cloud.