# Configure SLA escalation

1. Open the policy version (draft) in the editor.
2. On the stage, set **SLA (hours)** — e.g. `48`.
3. Set **On SLA breach** to one of:
   * **notify** — emit `task_expired` events; Caller decides what to do (default).
   * **auto-approve** — synthesize approve-decisions for all open tasks; advance.
   * **auto-reject** — synthesize reject-decisions; terminate the request.
   * **escalate** — add fresh approvers from the rules below.
4. If you chose **escalate**, an **Escalation rules** block appears. Click **+ Add rule** and add one or more rules (user / role / group / etc.) that resolve to the escalation approvers (e.g. the supervisors).
5. Save and activate.

The SLA monitor scans every `sla.checkIntervalSeconds` (default 300s). When a task's `due_at` passes, its stage's `on_breach` action fires once for the stage even if multiple tasks expire together.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openg2p.org/platform/platform-services/approval-workflow-engine/how-to/sla-escalation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.