{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/human-in-the-loop.durable-wait/",
    "json": "https://www.anchorterminal.com/niches/human-in-the-loop.durable-wait/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/human-in-the-loop.durable-wait/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/human-in-the-loop.durable-wait/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 7 | 32 | 19 | 7 |\n\n## What counts as done\n\nThe run survives a worker restart during the wait, resumes on the answer, receives only the answer for its own key, and an answer sent before the wait registered is not lost.\n\nMeasured, for our own tests: it resumes within 10 seconds of the answer.\n\nHow agents ask for it: wait for the manager's approval then continue; pause until the reviewer signs off, even overnight; resume the agent when they reply\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Temporal (Temporal Technologies Inc.)**: Workflow state and timers live in the event history, so a worker restart replays to the same wait; the workflow ID scopes the Signal and a Signal handled before the wait still sets the state. No resume latency is given, and the page rules out sub-second needs.\n- **withHuman (Metoro Inc)**: Requests persist server-side by ID, so an adapter can re-poll after a restart, and webhook mode sends a signed request.resolved retried for seven days. Each poll waits at most 30 seconds and no resume latency is stated.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **gotoHuman (gotoHuman UG (haftungsbeschränkt))**: The review is held server-side and the result is pushed by webhook, retried up to 7 times over hours with an Idempotency-Key, and keyed by reviewId. Resuming the run is the builder's code, no resume latency is stated, and fetching by ID is a Team-plan Reviews API.\n- **Hatchet (Hatchet Technologies, Inc.)**: The wait survives requeue and reads the event from the durable log; CEL filters plus a scope with lookback catch early answers. No resume latency is stated, Ruby lacks lookback, and issue 4714 (cross-scope waiter match) was fixed in August 2026.\n- **Inngest (Inngest Inc)**: Waits hold no process and resume on a matching event or a unique signal, matched by field or if expression. The docs say an event sent before waitForEvent listens is not matched (issue 1433), and no resume latency is stated.\n- **Orkes Conductor Human tasks (Orkes, Inc.)**: The task is held server-side by the Conductor cluster and completed by task ID, so worker restarts and early answers do not apply. No figure is given for resume delay after completion.\n- **Pushary (RalphNex OÜ)**: Questions persist server-side under a correlationId until answered or cancelled (connector questions close after 10 minutes), but the agent must keep polling wait_for_answer at 48 to 55 seconds a call, and a late reply cannot restart an ended turn.\n- **Restate (Restate GmbH)**: Signals, awakeables and promises survive retries and restarts, a signal resolved before the wait is stored, and awakeable IDs are unique. Resume latency is not stated, and issue 4566 (resolves lost in leadership changes) was fixed in April 2026.\n- **Trigger.dev (API Hero Ltd)**: Waitpoint tokens are held server-side, scoped by token ID with a per-token public access token, and complete over HTTP or the SDK. No resume latency is stated, and issue 2295 reported a run resuming 11 minutes after completion.\n\n- not this job: Big Arrow (Franz Enzenhofer (individual, Vienna)): bigarrow wait blocks in the agent's own shell; a card survives the session but nothing persists or resumes a run after a restart, and there is no correlation key beyond the process id.\n- not this job: Permit MCP Gateway (Permit Inc.): The wait lives in the open MCP call: an agent disconnect cancels the request and the default window is 5 minutes, so nothing survives a restart.\n\n## What stops agents finishing\n\n- event sent before the wait registers is never matched\n- resume delayed minutes by queueing or concurrency limits\n- signals cannot be resolved over HTTP in the released server\n- cross-scope events satisfy the wrong waiter\n\n## Around it\n\nBefore: workflow-automation.start-run. After: human-in-the-loop.approve-action.\n\n## Where this comes from\n\nWeight 19 of 100 in Human approval \u0026 handoff: 7 of 26 accounts, all GitHub issues on Inngest, Trigger.dev, Hatchet, Restate and LangGraph\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/human-in-the-loop.durable-wait.json, or the MCP tool get_use_case with id human-in-the-loop.durable-wait. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Pause a long workflow on a human answer and resume it once, with its state",
        "url": ""
      }
    ],
    "description": "Pause a long workflow on a human answer and resume it once, with its state: 2 companies fully do it, 7 with a limit, 32 carry the tag. Every listing in Human approval \u0026 handoff with the reason and a source.",
    "facts": null,
    "h1": "Pause a long workflow on a human answer and resume it once, with its state",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/human-in-the-loop.durable-wait/",
    "published": "",
    "section": "agents",
    "title": "Pause a long workflow on a human answer and resume it once, with its…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/human-in-the-loop.durable-wait/"
  },
  "tokens": {
    "markdown": 1300,
    "slim": 280
  },
  "version": 1
}
