kipn.ai
Shared workflow report

RedditScraper

Analyzed

Executive Summary
n8n
Production RiskHigh

External call with no timeout configured — A single slow external call can block the entire workflow execution. At high trigger frequency, accumulated stuck executions can exhaust the n8n execution queue.

Observability Gap

Side-effect node has no audit trail — If this action is disputed, replayed, or causes a data inconsistency, there is no structured record of what was sent, when, and with what data. Debugging requires cross-referencing n8n execution history with the external system's own logs.

84/ 100
Overall
Risk: HighCost: Low
Reliability
59
Security
100
Cost Risk
100
Observability
92
AI Governance
100
Naming
97
Complexity
100
Nodes
4
Edges
3
External calls
1
LLM nodes
0
AI via HTTP
0
Loops
0
Error handlers
0
Unreachable
0
Max depth
3
Workflow Graph
Graph
4 nodes · 3 edges
100%
click a node to highlight its upstream & downstream paths
Controls Matrix
Present Partial Missing
CheckDescriptionStatus
Failure Alerting

Failures silent — only visible in execution log

Missing
Retry on Failure

Transient failures cause permanent stops

Present
Request Timeouts

Slow providers can block execution indefinitely

Missing
Duplicate Prevention

Retry on write events creates duplicate records

Missing
Empty Response Handling

Zero-result lookups break downstream logic

Present
AI Output Limits

Output cost and parsing risk unbounded

N/A
AI Output Format

Free-form output will break downstream parsers

N/A
Activity Logging

Side effects unlogged

Missing
Write Deduplication

Webhook replays may create duplicate records

Present

Run this analysis on your own workflows

Break Points
1Missing timeoutRisk HighConfidence 90%1 node affected
Affected Nodes:
  • Scrape_Reddit_via_Browserless_JSON
What happens:

A single slow external call can block the entire workflow execution. At high trigger frequency, accumulated stuck executions can exhaust the n8n execution queue.

Recommended Fix:

Set a timeout under the node's Additional Options. A value of 10,000–30,000 ms (10–30 seconds) is a reasonable starting point for most APIs; adjust based on the provider's documented SLA.


2Missing error handlerRisk HighConfidence 85%2 nodes affected
Affected Nodes:
  • Scrape_Reddit_via_Browserless_JSON
  • Edit Fields[3753967f]
What happens:

Operators cannot tell from external signals that a run failed. Silent failures go undetected until a downstream system shows missing data or a user reports a problem.

Recommended Fix:

Connect a dedicated Error Workflow in workflow settings, or add a per-node onError: "continueErrorOutput" path that sends an alert via Slack, email, or a logging service.


4Missing audit logRisk MediumConfidence 70%1 node affected
Affected Nodes:
  • Scrape_Reddit_via_Browserless_JSON
What happens:

If this action is disputed, replayed, or causes a data inconsistency, there is no structured record of what was sent, when, and with what data. Debugging requires cross-referencing n8n execution history with the external system's own logs.

Recommended Fix:

After the write node, add a step that records the key fields of the action to a log — a Google Sheet row append, a database insert to an audit table, or a Slack message to a dedicated ops channel. Include: timestamp, action type, affected ID, and result.


6Fragile expressionRisk LowConfidence 75%1 node affected
Affected Nodes:
  • Edit Fields[3753967f]
What happens:

These expressions work reliably against test data where all fields are present. In production, fields may be absent, null, or differently typed — causing a runtime error or silent null propagation at the point of the expression.

Recommended Fix:
  • In `assignments.assignments[0].value`, change {{ $json.data.children }} to {{ $json?.data.children }}.
Raw Findings (6)
#Issue titleIssue descriptionAffected nodes
1ReliabilityExternal call with no timeout configured

Node "Scrape_Reddit_via_Browserless_JSON" makes an external call with no timeout parameter set. The n8n execution will wait indefinitely if the provider is slow or unresponsive.

Scrape_Reddit_via_Browserless_JSONHigh90%
2ReliabilityNo error handler or failure notification path

Workflow has 2 high-risk nodes (external calls or writes) with no configured error workflow and no inline notification path. If a production execution fails, the failure only appears in execution history.

Scrape_Reddit_via_Browserless_JSON, Edit FieldsHigh85%
3ReliabilityFinding: execute workflow blind spot

execute workflow node: "When Executed by Another Workflow". no error coverage — callee failures are invisible to this workflow. settings.errorWorkflow: absent. node.onError: absent. triggered condition: no_error_coverage

When Executed by Another WorkflowMedium90%
4ObservabilitySide-effect node has no audit trail

Node "Scrape_Reddit_via_Browserless_JSON" performs a write node: "scrape_reddit_via_browserless_json" (sideeffect: unknown_write) operation with no logging or audit trail detected downstream.

Scrape_Reddit_via_Browserless_JSONMedium70%
5NamingFinding: poor naming generic

1 node(s) use default/generic names.. Node "Edit Fields" (n8n-nodes-base.set) has a generic default name.

Edit FieldsLow90%
6ReliabilityFragile expression — likely to fail when production data shape differs from test data

Node "Edit Fields" contains expression(s) with risky patterns that assume fields are always present.

Edit FieldsLow75%

Catch workflow risks before they catch you