Printing Runtime Disconnected

Diagnose it

1. Check whether only one tab, one workstation, or all workstations are affected.
2. Confirm the runtime is still running and healthy.
3. Inspect browser and runtime timestamps around the disconnect.
4. Check sleep, user sign-out, upgrade, certificate expiry, port collision, and security software.
5. Verify client/runtime protocol versions.

Recovery pattern

Use connection states such as connecting, ready, degraded, and offline. Queue immutable jobs durably. Reconnect with exponential backoff plus jitter, authenticate again, request known job status where supported, and retry only jobs whose disposition is safe.

Never translate “socket closed” into “job failed.” The runtime may have accepted the job before the connection disappeared.

Prevent recurrence

• Add health and version telemetry without logging sensitive document content.
• Pause submissions during runtime upgrades.
• Handle workstation sleep and network changes explicitly.
• Alert after a bounded outage instead of retrying forever.

Portix evidence needed

Reconnect semantics, durable queue ownership, status lookup, idempotency, heartbeat, upgrade behavior, and log locations aren’t documented yet.

Verify

Disconnect during each job phase and confirm recovery produces neither loss nor duplicates.