{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/desktop-automation.triage-robot-failures/",
    "json": "https://www.anchorterminal.com/niches/desktop-automation.triage-robot-failures/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/desktop-automation.triage-robot-failures/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/desktop-automation.triage-robot-failures/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 3 | 3 | 6 | 3 |\n\n## What counts as done\n\nA list of failed or faulted jobs and stuck queue items in a time window, each with its process, robot, machine, error message and log link, from read-only calls.\n\nHow agents ask for it: which bots failed overnight; why is the queue backing up; show me the error on the last run\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- **Automation Anywhere (Automation Anywhere, Inc.)**: Failed runs come back from GetAutomationResult with error details and logs, and the Control Room API has Bot Execution Orchestrator, Audit, WLM queue and ACC failure-analytics groups. No time-window filter or read-only role was described on the pages read.\n- **Robocorp (Sema4.ai (full legal name not confirmed))**: List Process Runs, List Process Run Work Items and Get Process Run Status return run and work-item states, and Retry Work Item exists. Whether an API key can be read-only, and what error text a failed run carries, weren't documented on the pages read.\n- **UiPath (UiPath Inc.)**: GET Jobs filters on State eq Faulted, dates and Info text, with robot and release expandable, so failed jobs and their error messages come back. Queue items and a read-only token scope weren't on the pages read, and acc-02 had no MCP route for this.\n\n- not this job: Aura Autopilot (TribeVR Inc. (named in Aura's terms of service and privacy policy), trading as Ramen): No robot jobs or queues to query.\n- not this job: AutoCua (Ashish Yadav and contributors (ComputerUseAgent on GitHub)): No jobs, queues or robot logs to query.\n- not this job: AutoHotkey (AutoHotkey Foundation LLC): No jobs, queues or logs to read.\n- not this job: AutoIt (AutoIt Consulting Ltd): No jobs, queues or logs to read.\n- not this job: Beam (beam.win) (Noats, Inc.): No job, queue or log data.\n- not this job: Mage-VL-Cowork (Microsoft): No jobs, queues or logs to query.\n- not this job: Robot Framework (Robot Framework ry (Robot Framework Foundation), business ID 2754775-1, Helsinki): No jobs, queues or robots to query; results are local output files.\n\n3 listings in the category were added after this reading and aren't marked yet.\n\n## What stops agents finishing\n\n- no read-only token scope, so a triage agent holds run and delete rights\n- log endpoints return empty or time out on large tenants\n\n## Around it\n\nAfter: desktop-automation.start-existing-robot, messaging.post-message.\n\n## Where this comes from\n\nWeight 6 of 100 in Desktop \u0026 mobile app control: 3 of 45 accounts (UiPath forum); a support job builders asked for before vendors shipped it\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/desktop-automation.triage-robot-failures.json, or the MCP tool get_use_case with id desktop-automation.triage-robot-failures. 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": "Check failed robot jobs and queues and explain them",
        "url": ""
      }
    ],
    "description": "Check failed robot jobs and queues and explain them: 0 companies fully do it, 3 with a limit, 3 carry the tag. Every listing in Desktop \u0026 mobile app control with the reason and a source.",
    "facts": null,
    "h1": "Check failed robot jobs and queues and explain them",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/desktop-automation.triage-robot-failures/",
    "published": "",
    "section": "agents",
    "title": "Check failed robot jobs and queues and explain them | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/desktop-automation.triage-robot-failures/"
  },
  "tokens": {
    "markdown": 950,
    "slim": 230
  },
  "version": 1
}
