Skip to content

Conversation

@piyzard
Copy link
Contributor

@piyzard piyzard commented Aug 31, 2025

closes #128
/claim #128

🎯 Overview

This PR introduces a comprehensive detection rule for n8n Webhook Silent Failures - addressing critical silent data loss where incoming webhook requests fail to trigger workflows without proper error reporting or alerting. This represents the most dangerous type of n8n failure where business-critical automations silently fail to process incoming data, leads, or API events, potentially going undetected for days or weeks.

CRE Playground Links

CRE-2025-0178 Playground: Test Rule

📊 n8n Issues Covered

# Issue Type Example Error Pattern
1 Workflow Startup Failure 500 Internal Server Error: Workflow could not be started! Webhook execution failed
2 Database Connection Loss 500 Internal Server Error: Workflow could not be started! Database connection unavailable
3 Worker Context Loss Worker failed to find data for execution ID exec_789abc - execution context lost
4 Gateway Timeout 504 Gateway Timeout: webhook request exceeded 30 second timeout limit
5 Memory Allocation Failure 500 Internal Server Error: Workflow could not be started! Memory allocation failed
6 Service Unavailable Connection refused: n8n service unavailable on port 5678
7 Memory Exhaustion JavaScript heap out of memory during webhook processing
8 Permanent Data Loss Webhook data permanently lost - no recovery possible

🧪 Testing & Validation

image
cat rules/cre-2025-0178/test.log | preq -r rules/cre-2025-0178/n8n-webhook-silent-failure.yaml -d

🎬 Demo Environment

Repo link: https://github.com/prequel-dev/cre/tree/main/examples/n8n-cre-demo

Screencast.from.2025-08-31.17-01-45.mp4

Features:

  • Real n8n workflow automation simulation with webhook failures
  • Professional production environment simulation with actual failure scenarios
  • Automated webhook failure log generation with realistic patterns
  • Docker containerized environment for consistent testing
cd cre/examples/n8n-cre-demo
./start.sh

References

@piyzard
Copy link
Contributor Author

piyzard commented Oct 22, 2025

@Lyndon-prequel can i get a review on this ?

@amanycodes
Copy link
Contributor

amanycodes commented Oct 27, 2025

@piyzard thanks for the submitting a Rule! could you please provide working prequel playground link? the current one just opens up the landing page and also if you don't mind add me the test repo link. The current one points to the actual prequel-dev/cre repo and showing 404.
here's my username: amanycodes

- metadata:
kind: prequel
id: N8nWh3kP7qRzYvMr2aLfJ8
hash: ZpQ9Lm4Zk8TnVb2Ry6HwGs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hash is not a valid field

event:
source: cre.log.n8n
match:
- regex: 'Workflow could not be started'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this regex expression can be improved:
"(?i)(Workflow could not be started|Database connection unavailable|execution context lost|Connection refused|504 Gateway Timeout|heap out of memory|Webhook data permanently lost)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

n8n: Reproduce A High-Severity Failure & Write a CRE Rule [Multiple Winners] [Submit by August 31 11:59 pm ET]

2 participants