Merged
Conversation
…e categories and tags for workflow automation issues
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
CRE Playground Links
Playground Link
test.log
rules/cre-2025-0179/n8n-silent-data-loss.yamlrules/cre-2025-0179/test.logDemo Environment
https://github.com/Sahelisaha04/n8n-cre-demo (invitation send)
Screencast.from.2025-08-31.23-57-29.mp4
Testing & Validation
Test Results
Validation Steps
Fixes #128
/claim #128