# Decide what happens when nobody answers

> Decide what happens when nobody answers: 1 companies fully do it, 8 with a limit, 16 carry the tag. Every listing in Human approval & handoff with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/human-in-the-loop.timeout-policy/
- Markdown: https://www.anchorterminal.com/niches/human-in-the-loop.timeout-policy/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/human-in-the-loop.timeout-policy/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/human-in-the-loop.timeout-policy/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 8 | 16 | 11 | 4 |

## What counts as done

At the deadline the request ends with the configured outcome, which defaults to deny, the agent gets a typed timeout distinct from rejection, and an escalation or reminder is sent when configured.

How agents ask for it: if I don't answer in an hour, cancel; escalate to my lead after 30 minutes; don't do it if no one approves

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **withHuman (Metoro Inc)**: Every request must carry a timeout of 1 second to 7 days and ends as expired, distinct from denied, and the adapter must not run the call. Escalation paths contact further reviewers after set times.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Hatchet (Hatchet Technologies, Inc.)**: A deadline needs a SleepCondition in an or group with the event condition; the task then checks which fired. No default outcome, no typed timeout and no escalation or reminder.
- **Inngest (Inngest Inc)**: Every wait takes a timeout and resumes with null or undefined, distinct from a rejection event. What a timeout means and any reminder or escalation are the builder's code; there is no default deny.
- **Orkes Conductor Human tasks (Orkes, Inc.)**: slaMinutes per assignment escalates down a chain of assignees, TERMINATE fails the workflow and a TIMED_OUT trigger can notify. The default is LEAVE_OPEN and 0 never expires, so an unset deadline does not deny.
- **Permit MCP Gateway (Permit Inc.)**: A timeout always rejects (default 5 minutes) and History marks it timed out, but the window is too short for overnight review, extends only by a +5 min button, and the agent's error is not documented as distinct from a rejection.
- **Pushary (RalphNex OÜ)**: An expired status is distinct from deny and is documented as no approval, and an unanswered question can trigger a phone call. Expiry follows server policy with no per-request deadline (timeoutMs sets only one call's wait), and the default deny rests on the skill telling the agent so.
- **Restate (Restate GmbH)**: orTimeout throws a TimeoutError distinct from a rejection, and the timer survives restarts. Without it the wait never ends; no default outcome, reminder or escalation exists.
- **Temporal (Temporal Technologies Inc.)**: The wait takes a timeout and returns a timeout path distinct from a rejection, and the page shows escalation and multi-level chains. All of it is builder code; with no timeout the workflow waits indefinitely.
- **Trigger.dev (API Hero Ltd)**: createToken takes a timeout and forToken returns ok: false with an error, distinct from a rejected output. Omitting timeout means no timeout at all (the map's named blocker), and there is no default outcome or escalation.

- not this job: Big Arrow (Franz Enzenhofer (individual, Vienna)): Cards have no time limit by design; they stay until answered, closed or stopped. Arrows end after their duration but report no timeout outcome or escalation.
- not this job: gotoHuman (gotoHuman UG (haftungsbeschränkt)): The create-review reference has no deadline, expiry or timeout field, and fetch-review knows only pending and responded states, so a request never ends by itself.

## What stops agents finishing

- no timeout at all, so the wait never ends (Trigger.dev token without timeout, Restate without orTimeout)
- default proceeds on best judgement
- window too short for overnight review (Permit 5 minutes)

## Around it

Before: human-in-the-loop.reach-approver. After: notifications.push.

## Where this comes from

Weight 11 of 100 in Human approval & handoff: 4 of 26 accounts (AskUserQuestion proceeding after 60 seconds, timeout-as-deny in n8n, Inngest timeouts); buyer check 2

As data: https://www.anchorterminal.com/api/v1/use-cases/human-in-the-loop.timeout-policy.json, or the MCP tool get_use_case with id human-in-the-loop.timeout-policy. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
