Control

Emergency stops

Stop a run, a workload or a tool in every mode, record-only included.

Alerta check crossesits thresholdApprove stopadmin or lead;Stop now: adminBSigned bundlecarries the stopsin forceGateways checkevery 15 sby default403, recordednothing sentevery mode
From an alert to a refused request · a person approves, or automatic action after its wait
THE GATEWAY · NEVER STOPPED WHOLEapplicationevery key it hasworkloadX-Saible-Workflowor the hash of its system promptagentX-Saible-Unita header the tool sendsrunX-Saible-Runa header the tool sendsNever a person: a value that looks likepersonal data is refused.
What a stop can name · the widest is one application
Do it
  1. 1Open Emergency stops under Control.
  2. 2An alert waiting? Click Approve stop, or Dismiss and say why.
  3. 3To stop now: in Stop, choose run, agent, workload or application, type the id and the reason, click Stop now.
  4. 4To lift: in In force, click Lift and say why.
For your agents

This topic is also written as Agent Skills your agents can load: emergency-stops, gateways, gateway-extras. Ask us for them.

Next · Gateway · AccessKeys and who holds them →