skills.rest
Rub-git
Rub-gitCOMMUNITY
Explore all skills by this author →
GitHub

debugging-executions

Diagnose failed n8n workflow executions by re-running paths and retrieving node parameters.

Updated Jul 3, 2026
Search Tags:#workflow#debugging#analysis#execution#n8n
One-click install
npx skills add https://github.com/Rub-git/n8n-auto --skill debugging-executions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-executions
Source: https://github.com/Rub-git/n8n-auto/tree/main/packages/%40n8n/instance-ai/skills/debugging-executions
Command: npx skills add https://github.com/Rub-git/n8n-auto --skill debugging-executions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Debugging failed or incorrect workflow executions can be challenging. This skill provides precise tools to diagnose issues quickly.

Core Features & Use Cases

  • Execution Analysis: Analyze failed or incorrect executions with detailed tools.
  • Quick Diagnosis: Identify and resolve execution failures and unexpected outcomes.
  • Use Case: When a user reports a failed workflow, this skill can re-run the execution or retrieve node parameters to pinpoint the issue.

Quick Start

Run executions(action="run") to re-run a failing workflow path.

Frequently Asked Questions about debugging-executions

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

FAQPage Schema
How do I debug failed n8n workflow executions?▼

To debug failed n8n workflow executions, you can re-run the failing workflow path or retrieve specific node parameters to pinpoint the root cause. This provides detailed diagnostic data to identify why the execution failed.

Why does my n8n workflow have unexpected outputs or empty parameters?▼

Unexpected outputs or empty parameters in an n8n workflow indicate incorrect node configurations or upstream execution failures. Analyzing the execution path helps trace where the data flow diverged from expected results.

What is the best way to diagnose incorrect n8n workflow outputs?▼

The best way to diagnose incorrect n8n workflow outputs is to analyze the failed execution paths and retrieve node parameters. This isolates the specific nodes generating the unexpected data.

Can I re-run a failed n8n workflow execution to test fixes?▼

Yes, you can re-run failed n8n workflow executions to test fixes. Re-running the execution path allows you to verify if parameter adjustments resolved the unexpected outcomes or empty parameters.

Does this execution analysis require access to n8n execution tools?▼

Yes, n8n execution analysis requires access to execution tools and the ability to re-run workflows or retrieve node parameters. This environment access is necessary to diagnose failed paths accurately.

Related Skills

Explore More Software Engineering Skills→
pokgakpokgak

n8n

List, update, trigger, and retry n8n workflow executions via API.

Community
Intermediate
HustleDanieHustleDanie

n8n-expression-syntax

Diagnoses and fixes n8n expression syntax errors in {{ }} code.

Community
Intermediate
PinpongTpPinpongTp

n8n

Create, test, execute, and optimize n8n workflows via the n8n API.

Community
Advanced
pessinipessini

n8n-mcp-tools-expert

Guide n8n-mcp MCP tool selection, configuration, and workflow management.

Community
Advanced