{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "banmu123-loomflow--debug-failing-workflow-with-trace",
 "repo": "banmu123/LoomFlow",
 "repo_url": "https://github.com/banmu123/LoomFlow",
 "repo_slug": "banmu123-loomflow",
 "title": "Find why a workflow run failed and fix it from the trace",
 "page_title": "How to find why a workflow run failed and fix it from the trace with Loom Flow",
 "summary": "Use the per-node execution trace and the canvas assistant to locate the failing step and its likely fix.",
 "who": "A builder whose workflow returns an error or stalls and who needs to know which node caused it.",
 "problem": "A failed multi-step run is hard to diagnose when you only see a final error message.",
 "outcome": "A named failing node with its status, duration, and error, plus a root-cause explanation and a suggested fix.",
 "steps": [
  "Run the workflow that is failing and open its execution trace after the run ends",
  "Read the timeline to find the node with the error, its duration, and token usage",
  "Ask the canvas AI assistant why the run failed and request root cause and fix suggestions",
  "Apply the suggested change to the canvas, then run the workflow again"
 ],
 "agent_prompt": "Using LoomFlow at https://github.com/banmu123/LoomFlow, open the execution trace for the failed run <runId> of workflow <workflowName> and ask the canvas assistant for the root cause. Expected output: the failing node name, its error, and a proposed fix. Verify by re-running the workflow after applying the fix and confirming the trace shows all nodes completed.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "The assistant's root-cause answer depends on the model you configured, so confirm any suggested fix against the trace before applying it.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A machine with Docker and Docker Compose installed, plus git and a terminal (the README says 1 GB RAM is enough)",
  "An API key for an LLM provider such as DeepSeek, or any OpenAI-compatible endpoint, added later through the admin UI",
  "A web browser to open http://localhost:5000"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/banmu123-loomflow/debug-failing-workflow-with-trace/",
 "md": "https://dedupedai.com/use-cases/banmu123-loomflow/debug-failing-workflow-with-trace/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/banmu123-loomflow--debug-failing-workflow-with-trace.json",
 "api_version": "v1"
}