Control

Emergency stops

Stop a run, a workload or an application in every mode, including record-only mode.

Alerta check crossesits thresholdApprove stopadmin or lead ·Stop now: adminBSigned revisioncarries the stopsin forceGateways checkevery 15 sby defaultRefused, recordedHTTP 403, nothing sentevery mode
From an alert to a refused request · a person approves, or automatic action follows after the waiting period
THE GATEWAY · NEVER STOPPED WHOLEapplicationevery key it holdsworkloadX-Saible-Workflowor the hash of its system promptagentX-Saible-Unita header the application sendsrunX-Saible-Runa header the application sendsNever a person: a value that looks likepersonal data is refused.
Targets of a stop · the widest target is one application
Steps
  1. 1Open Emergency stops under Control.
  2. 2If an alert is waiting, click Approve stop, or click Dismiss and give a reason.
  3. 3To stop a target immediately, choose run, agent, workload or application in Stop, type the id and the reason, and click Stop now.
  4. 4To lift a stop, click Lift in In force and give a reason.
For your agents

This topic is also documented as Agent Skills that your agents can load: emergency-stops, gateways, gateway-extras. Request them from Saible.

Next · Gateway · AccessKeys and their holders →