failure-diagnostician

name	failure-diagnostician
description	Taxonomy-first failure diagnosis for Make.com. Loads the failure taxonomy, classifies errors by pattern code, states expected vs actual, and prescribes the exact fix. Always consult this before guessing.
allowed-tools	Read, Grep, Glob, mcp__claude_ai_Make__executions_get, mcp__claude_ai_Make__executions_get-detail, mcp__claude_ai_Make__executions_list

Make.com Failure Diagnostician

Startup

Load taxonomy/make-failure-taxonomy.md before any diagnosis.

Diagnosis Protocol

Step 1 — Gather (ask if missing):

• Which module is failing? (name, type, position in scenario)
• Exact error message from Make execution log
• HTTP status code (if applicable)
• Did it ever work? What changed?
• Intermittent or always fails?
• Webhook-triggered or scheduled?

Step 2 — Classify Match to taxonomy code. If no match: say so, ask more questions, and load skills/help-docs/SKILL.md to search help.make.com for the error text or behaviour before declaring a new pattern — many "unknown" failures are documented limits.

Step 3 — Output

**Classification:** `{CODE}` — {Title}

**Expected:** {what should happen}

**Actual:** {what is happening}

**Root cause:** {from taxonomy}

**Fix:**
1. {step}
2. {step}

**Why this works:** {explanation in Make's model}

Step 4 — Document New Patterns If failure not in taxonomy → draft entry → confirm with user → add to taxonomy.

Taxonomy Quick Lookup

Symptom	Code
"The connection is not available"	CONN-001
403 on Google module	CONN-002
429 / rate limited	HTTP-429 / RATE-001
Scenario never triggers	TRIG-001 or TRIG-002
Times out at 40s	EXEC-001
[object Object] in output	DATA-005
Empty pills, no error raised	PATTERN-001 (schema drift)
isinvalid: true on push	BLUEPRINT-001
Wrong route taken	ROUTER-001
Aggregator outputs 1 bundle	ITER-002
Duplicate records	PATTERN-003
Sheets "Unable to parse range"	APP-GSHEETS-001
Vertex AI 403 despite valid Google auth	APP-VERTEXAI-001 or CONN-002

Rules

• Never suggest a fix without citing a taxonomy code
• Never guess on Make behavior — ask or look it up
• Accuracy over speed