Sculptured docs

Connection interruptions

What keeps going, what waits and what happens on reconnect when the computer running your agents loses its connection mid-run.

A lost connection to Sculptured does not stop agents on a computer that is still running. The runner keeps their events and sends them when it reconnects. While the connection is down, the app shows the last known activity.

Sleep and shutdown are different: sleep pauses the agents, and a shutdown ends their processes. Keep the computer awake for uninterrupted work.

Identify the interruption

ConnectionIf it dropsWhat you see
Your browser ↔ SculpturedOnly the page stops updating. Agents are not affected."reconnecting" in the status line. On a team page that never got its first update: "Live updates for … aren't arriving."
Your computer ↔ SculpturedAgents keep running on the computer. Sculptured cannot see them for a while.Agents show unknown. Status reads "reconnecting".
Sculptured itself restartsThe computer reconnects to the new server on its own.A short "reconnecting", then agents return.

What keeps going

sequenceDiagram
  participant A as Agent
  participant R as Runner on your computer
  participant S as Sculptured
  participant Y as You
  A->>R: "request_input: Which colour?"
  R->>S: "the agent's call"
  S-->>Y: "question: needs you"
  Note over R,S: "connection drops"
  R->>R: "keeps the call, keeps recording events"
  Y->>S: "answer: Green"
  S->>S: "answer kept, question still open"
  Note over R,S: "connection back"
  R->>S: "replayed events, the call again"
  S->>R: "the kept answer, once"
  R->>A: "Green"

What you see while it is away

What you can still do

Start a team or send a message
If the connection dropped less than 45 seconds ago, Sculptured waits for the computer to come back before it gives up. So a team started during a short drop launches as soon as the computer is back. If the computer stays away, or has been gone longer, the action fails and says why: "Sculptured could not reach this agent's host: …". A message that could not be sent is recorded as not delivered.
Stop an agent or the team
Sculptured accepts stop requests while the computer is offline. The agent shows stopping, with "Stops as soon as its computer reconnects". When the computer returns, Sculptured stops it. If the agent had already ended meanwhile, it records "Its computer reconnected; the agent had already ended".
Answer a question
Sculptured records your answer while the computer is offline and delivers it when the runner reconnects.
Edit the design
Works as usual. Design edits are saved by Sculptured, not on the computer.

When it comes back

The runner reconnects on its own. It checks the connection every 25 seconds, gives up on a silent one after 75 seconds, and retries every few seconds. On reconnect it tells Sculptured which agents are still alive.

On reconnectResult
The agent is still runningIt returns to running. Its events since the drop arrive.
The agent was stopped while offlineIt is stopped now.
The agent's process ended, for example after a rebootIt needs attention, with the reason. If the team is still set to run, the board asks "N agents stopped mid-work. Resume them where they left off?" with Resume, Start fresh and Leave stopped. Nothing relaunches until you answer.

If live updates never arrive

If a team page stays on "Connecting to …" for 8 seconds, it says "Live updates for … aren't arriving." Sculptured keeps trying in the background. The agents are not affected. This is usually a dropped network connection, or a network that blocks live connections, such as some company proxies. Use Try again, or Open the Design board to keep working on the design.

If the computer was disconnected from your account

If you remove a computer from the Computers page, its runner stops with "This computer was disconnected from its Sculptured account." Copy a new connect command from Computers and run it on that computer. See Connect a computer.

Next steps