> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-10-10 — Human tasks: one way a person decides

> Every wait on a person is a human task with a due date that ends in cancel, never in approval; recordDecision and the shared-token approval route are removed; approval.resolved may carry canceled.

**2026-10-10**

Human tasks, Increment 1: every wait on a person completes through one transaction.

## Summary

Every place Forge waits on a person — a Trust Fabric approval, a workflow human step, an agent's `human_ask` question, an Architect plan and a synthesis confirmation — is now a **human task**. A person decides it in Forge Console, in Slack or by email reply, and every decision runs through one completion transaction that checks who may act, records the decision and applies it together. A task has a due date that ends in a declared outcome: it is **canceled**, never approved.

## Breaking

* `POST /api/v2/governance/recordDecision` is removed and now answers `404`. No API key or External App could ever hold `approvals:approve`, so it never succeeded; a person decides in Forge Console, Slack or email. Hand a held run to a person with the `handoff` from [`GET /api/v2/runs/getTrustStatus`](https://docs.gloo.com/forge/reference/http-api/runs/getTrustStatus).
* `POST /api/workflow/approval` (the shared-token approval route) is removed and now answers `404`. `MC_APPROVAL_API_TOKEN` is no longer read.
* Approvals are canceled instead of auto-rejected. An approval nobody decides is escalated to its policy's releasers at its due date (72 hours, or its SLA window) and canceled at its final due date (`cancelReason: "due_date"`). When a run ends, its pending approvals are canceled (`run_ended`). A canceled workflow hold fails its node with `approval_canceled`.
* The `approval.resolved` webhook event may carry `decision: "canceled"`.
* A workflow human step with no authored timeout is now due after 72 hours, escalates to `approvals:approve` holders for 72 more, and then fails. A step that authors both `timeout` and `onTimeout` keeps that deadline, and its `onTimeout` decides the end (`skip` and `fail` do not escalate). A `timeout` alone, such as the 5-minute default the workflow builder sets on every step, is not a human deadline and gets the 72-hour default.
* An agent's `human_ask` with no person to ask (no resolvable chat author, run launcher or named worker) is refused with `HUMAN_ASK_NO_CANDIDATE` and asks nobody.
* An unanswered `human_ask` question now expires after 72 hours instead of 7 days.

## Changed

* Approving a hold that requires an independent approver, or a financial or destructive tool call, needs a signed-in Forge Console session. Slack and email answer with a link to the item in Forge; rejecting still works from Slack and email.
* Once this deploy's human-task backfill completes, only the people a task asks can decide it. A platform approver who is not asked is refused with a reason; an administrator can reassign the task.
* When an item asks more than one person, one of them can **Claim** it in My Work; nobody else can decide it until they release it or its follow-up date passes.
* **Decline** ("not me") needs a reason. When nobody else is left, the item escalates, or is canceled with `cancelReason: "declined"`.
* Reassigning a workflow step or approval needs `approvals:approve` where the item lives; the current assignee can no longer reassign their own item (they decline it instead). A reassignment keeps only people who can act on the item.
* A Slack reject now applies at once instead of being queued, so a refusal shows in the Slack modal. Every Slack refusal is answered to the person who clicked; a refused email reply gets one answer saying why.
* The policy's releasers are asked at escalation, or at once when none of the approvers named first can release the hold; they are no longer messaged when the hold is created.
* Each person an item asks gets their own Slack DM.
* `GET /api/v2/runs/getTrustStatus` reports a canceled hold as `state: "rejected"` (message "Approval canceled") and its `continuation` as `refused` / `approval_rejected`. The response schema is unchanged.

## Deploy note

Approvals and tasks pending at deploy keep their state and get a due date at least one hour after the deploy. No reminder or escalation is sent for them at deploy time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.