debug-workflow

Diagnose failing workflow executions by identifying the failing node and root cause from logs.

1|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill debug-workflow-bibektimilsina00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-workflow
Source: https://github.com/bibektimilsina00/fuse_monorepo/tree/main/.agents/skills/debug-workflow
Command: npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill debug-workflow-bibektimilsina00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose failing or misbehaving workflow executions by locating the exact error point and translating logs into actionable fixes.

Core Features & Use Cases

  • Execution-log forensics: Uses an execution ID to retrieve ordered log entries and pinpoint the node where errors first appear.
  • Execution-path tracing: Maps logged node IDs back to the workflow graph to reconstruct the path from Start through the failed node.
  • Common failure pattern guidance: Provides targeted causes and remediations for frequent issues like missing required fields, credential problems, template/interpolation errors, HTTP 422s, and nodes blocked by graph conditions.
  • Node-level configuration and implementation checks: Guides inspection of the failing node’s resolved properties and (when needed) its execute() implementation to confirm why success is not returned.

Quick Start

Run the debug-workflow skill with an execution ID or a description of the failure (including any error message) to receive a structured report with the failing node, root cause, and the specific fix to apply.

Frequently Asked Questions about debug-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the exact node causing a workflow execution failure?

To find the exact node causing a workflow execution failure, retrieve ordered execution logs using the execution ID to locate where errors first appear, then map that node ID back to the workflow graph to pinpoint the failure point and apply the recommended fix.

Why does my agentic workflow node stay blocked and never start?

A workflow node stays blocked and never starts due to unmet graph conditions or path requirements preventing execution. Diagnosing this requires tracing the execution path from Start through the graph to identify why the required conditions were not satisfied.

How do I debug template expression and missing field errors in execution logs?

Debug template expression and missing field errors in execution logs by extracting the error payload details from the failed node, then inspecting the node's resolved properties to confirm why required fields are missing or template interpolation fails.

What is the best way to diagnose HTTP 422 request format problems in a workflow?

The best way to diagnose HTTP 422 request format problems in a workflow is to retrieve the execution logs, extract the error payload from the failing HTTP node, and inspect the resolved request properties to identify and fix the malformed data format.

Can I trace a failed workflow execution path using only an execution ID?

Yes, you can trace a failed workflow execution path using an execution ID by fetching the ordered log entries via SQL or API, mapping the logged node IDs to the workflow graph, and reconstructing the exact route from Start to the failed node.

How do I fix credential selection errors in a failing workflow node?

Fix credential selection errors in a failing workflow node by retrieving the execution logs to confirm the credential failure, then inspecting the node's configuration to ensure the correct credentials are selected and properly authenticated for that specific action.