Skip to main content

​
Node Inputs

​
Required Fields

Error Message:
The error message to display when the workflow fails.
Example: "Required data validation failed: Email address is missing"

​
Optional Fields

Error Code:
A custom error code for categorization.
Example: "VALIDATION_ERROR" Error Details:
Additional details about the error as a JSON object.
Example: 
{
  "field": "email",
  "reason": "missing_required_field",
  "expected": "valid email address"
}
Stop Workflow:
Whether to stop the entire workflow or just the current branch.
Example: true
Default: true

​
Node Output

Failure Information:
Details about the intentional failure (typically captured in workflow error logs). Example Output: 
{
  "status": "failed",
  "error_message": "Required data validation failed: Email address is missing",
  "error_code": "VALIDATION_ERROR",
  "error_details": {
    "field": "email",
    "reason": "missing_required_field",
    "expected": "valid email address"
  },
  "failed_at": "2024-10-19T10:30:00Z",
  "node_id": "fail_node_123"
}

​
Node Functionality

The Fail Node:
  • Intentionally fails the workflow with a custom error message.
  • Useful for data validation and business rule enforcement.
  • Provides clear error messages for debugging and monitoring.
  • Supports custom error codes for categorization.
  • Can include detailed error context as JSON.
  • Typically used after conditional checks to stop invalid workflows.
  • Helps maintain data quality and workflow integrity.

​
Common Use Cases

Data Validation:
  • Stop workflow if required fields are missing
  • Fail if data doesn’t meet quality standards
Business Rules:
  • Enforce business logic constraints
  • Prevent invalid operations
Error Handling:
  • Create clear failure points in complex workflows
  • Provide meaningful error messages for troubleshooting
⌘I