/approvals) is a centralized queue for all pending human decisions. When a governance policy triggers an approval gate during workflow execution, the workflow pauses and an approval card appears here.
Pending Queue
All approvals awaiting resolution, sorted by urgency. Each card shows:| Field | Description |
|---|---|
| Workflow | Which workflow the approval belongs to |
| Step | The specific step that triggered the gate |
| Policy reason | Why the approval was triggered (budget threshold, HITL gate, policy rule) |
| Requesting agent | The agent that was executing when the gate fired |
| Time since creation | How long the approval has been waiting |
Urgency Indicators
Approvals age. The longer they sit, the more urgent they become. Escalation tier badges provide visual triage priority:Tier 1 — Standard
New approval, under 1 hour. No escalation badge.
Tier 2 — Elevated
1h+ unresolved. Amber badge, Slack reminder fires.
Tier 3 — Critical
24h+ unresolved. Red pulsing badge, urgent escalation.
Resolution
Resolve an approval by clicking Approve or Reject:- Approve — optionally add scope constraints. The workflow step resumes immediately.
- Reject — requires a reason (stored in the audit trail). The step fails, and what happens next depends on the step’s failure policy in the
.lobsterXdefinition.
In-Run Resolution
Approvals can also be resolved directly from the run detail page, in context with the full execution timeline visible. The run sidebar shows pending approval gates with Approve/Reject buttons alongside the step list and audit timeline.Multi-Surface
The same approval appears in Burgundy, Slack (if syndicated), and the Platform API. Resolving on any surface resolves everywhere.| Surface | Mechanism |
|---|---|
| Burgundy | This page or the run detail sidebar |
| Slack | Interactive approval message with Approve/Reject buttons |
| Platform API | Programmatic resolution via the approvals endpoint |