Skip to content

N8N - CRE Detection#135

Merged
tonymeehan merged 3 commits intoprequel-dev:mainfrom
Sahelisaha04:cre-2025-0919-n8n
Sep 3, 2025
Merged

N8N - CRE Detection#135
tonymeehan merged 3 commits intoprequel-dev:mainfrom
Sahelisaha04:cre-2025-0919-n8n

Conversation

@Sahelisaha04
Copy link
Copy Markdown
Contributor

@Sahelisaha04 Sahelisaha04 commented Aug 27, 2025

CRE-2025-0179: N8N Silent Data Loss Detection

Overview

This pull request implements a Critical Runtime Event (CRE) detection rule for N8N workflow automation platform silent data loss scenarios. The rule identifies critical failures where N8N workflows are cancelled mid-execution leading to potential data integrity issues.

Problem Statement

N8N workflow automation systems can experience silent data loss when workflows are cancelled or terminated unexpectedly during execution. This creates critical scenarios where:

  • Workflows cancel mid-execution due to timeouts or system issues
  • Data processing is incomplete but appears successful
  • Silent data loss occurs without proper error reporting
  • Production systems continue operating with compromised data integrity

CRE Playground Links

Playground Link

test.log

image
  • Rule File: rules/cre-2025-0179/n8n-silent-data-loss.yaml
  • Test Logs: rules/cre-2025-0179/test.log

Demo Environment

https://github.com/Sahelisaha04/n8n-cre-demo (invitation send)

./start.sh

 cat logs/docker/failure-combined.log | preq -r cre-2025-0179/n8n-silent-data-loss.yaml -d
 cat logs/docker/cre-test.log | preq -r cre-2025-0179/n8n-silent-data-loss.yaml -d
Screencast.from.2025-08-31.23-57-29.mp4

Testing & Validation

Test Results

  • ✅ CRE rule successfully detects N8N silent data loss patterns
  • ✅ Sequence detection works within 120-second window
  • ✅ Realistic log patterns trigger appropriate alerts
  • ✅ Demo environment generates authentic failure scenarios

Validation Steps

  1. Rule Syntax Validation: Preq CLI validates YAML structure
  2. Pattern Matching: Test logs trigger detection successfully
  3. Demo Environment: Docker containers generate real N8N logs
  4. End-to-End Testing: Complete workflow from failure to detection

Fixes #128
/claim #128

…e categories and tags for workflow automation issues
@tonymeehan tonymeehan merged commit 5dabcb8 into prequel-dev:main Sep 3, 2025
2 checks passed
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