Skip to content

Stop and Error

What it does: Stops your workflow immediately and shows a helpful error message when something goes wrong.

Perfect for: Data validation • Error handling • Debugging workflows • Quality control

graph LR
    A[🔍 Check Data] --> B[❌ Problem Found]
    B --> C[🛑 Stop & Error]
    C --> D[📝 Error Report]

    style A fill:#e1f5fe
    style B fill:#ffebee
    style C fill:#ffcdd2
    style D fill:#f3e5f5

Simple process: Check finds problem → Stop & Error triggered → Workflow stops with helpful error message

Data validation - Stop if scraped data is incomplete or wrong format Quality control - Stop if content doesn’t meet your standards Permission errors - Stop if browser permissions are denied API failures - Stop if external services aren’t working Debugging - Stop at specific points to check what’s happening

Scenario: Stop workflow if scraped article has no title or is too short

Configuration:

{
"message": "Article validation failed: {{data.title ? 'Content too short' : 'Missing title'}}",
"errorType": "validation_error",
"severity": "error"
}

Input data that triggers error:

{"title": "", "content": "Short text", "wordCount": 5}

Error message shown:

❌ Article validation failed: Missing title
Error Type: validation_error
Severity: error
Timestamp: 2024-01-17 10:30:15

Be specific about the problem:

{"message": "Missing required field: email address"}

Include helpful context:

{"message": "Content too short: {{data.wordCount}} words (minimum 100)"}

Use clear, non-technical language:

{"message": "Could not connect to the website. Please check your internet connection."}

Add severity levels:

  • “info” - Just for information
  • “warning” - Something might be wrong
  • “error” - Definite problem (default)
  • “critical” - Serious issue that needs immediate attention

Data Validation Pattern:

[Get Data] → [IF Check] → [Stop & Error if invalid]
[Continue if valid]

API Error Handling:

[HTTP Request] → [Check Response] → [Stop & Error if failed]
[Process if successful]

Quality Control:

[Extract Content] → [Validate Quality] → [Stop & Error if poor]
[Continue if good]

Error triggers too often: Check your validation conditions - they might be too strict

Error messages not helpful: Add more specific details about what went wrong and how to fix it

Workflow stops unexpectedly: Review the data being passed to the Stop & Error node

Related nodes: IfFilterWait

Common workflows: Data Validation PatternsError Handling StrategiesQuality Control Workflows

Learn more: Workflow DebuggingFlow Control BasicsMulti-Step Workflows