Skip to main content

​
Overview

Cyberdesk automatically quarantines a desktop when Cyberdriver becomes unreachable at run startup or while a run is executing. Quarantine prevents additional work from being assigned to a machine that needs operator attention. Cyberdesk confirms the outage with a lightweight display-dimensions request. It makes one request first and retries only after a failure, for a maximum of three attempts with a 0.5-second pause between attempts. The first successful response means the machine is reachable and stops the check. If all three attempts fail, Cyberdesk:
  • Ends the affected run with an error status and repair instructions.
  • Marks the desktop disconnected and unavailable.
  • Clears its stale Cyberdriver routing target.
  • Removes it from every desktop pool.
  • Immediately sends a downed_machines webhook when Downed machine alerts is enabled for that desktop.
Quarantine and pool removal apply even when machine alerts are disabled. The alert setting controls only webhook and Slack delivery.

​
Run Error

The affected run explains what Cyberdesk detected and changed:
Cyberdriver became unreachable on this machine after 3 display checks. Cyberdesk marked the machine disconnected and unavailable and removed it from all pools to prevent further runs. Repair or restart Cyberdriver on the machine, verify that it reconnects, then manually re-add it to the appropriate pools.
Remaining runs in the same chain or session are cancelled through the normal failure flow.

​
Slack And Webhook Alerts

When Downed machine alerts is enabled, quarantine immediately publishes the existing downed_machines event. Its reason identifies the run-time Cyberdriver outage and the quarantine action. The payload still contains the organization’s full current set of monitored downed machines. The recurring monitor is a fallback, not a second notification. Cyberdesk records the down transition before publishing, so a monitor check one second later sees the machine as already down and does not send a duplicate event. If immediate delivery fails, Cyberdesk releases the alert claim so the next monitor check can retry it. See Downed Machines Webhook to connect alerts to Slack or another destination.

​
Restore A Quarantined Machine

  1. Open the affected Windows desktop and repair or restart Cyberdriver.
  2. Verify that the desktop reconnects in Dashboard -> Desktops.
  3. Confirm that basic desktop actions work.
  4. Manually add the desktop back to the appropriate pools.
Cyberdesk does not restore removed pool memberships automatically. This ensures an operator confirms the machine is healthy before it returns to pooled automation. Cyberdesk also does not send a recovery webhook. A successful run-start dimensions check clears the internal alert state, allowing a later outage to notify you again.

​
Scheduled Monitoring

The recurring downed-machines monitor continues to check opted-in desktops even when no run is active. It uses the same maximum of three attempts and stops after the first successful dimensions response. Scheduled monitoring sends alerts but does not quarantine desktops or remove them from pools. Automatic quarantine is limited to confirmed Cyberdriver failures encountered by a run.