End Failure
Learn about End Failure nodes and how they terminate workflows with failure status
The End Failure node terminates the workflow execution with a failure status. It provides a way to explicitly mark a workflow as failed when certain conditions are met or when an error state is encountered.
Workflow Termination
Immediately stops workflow execution with failure status
Error Handling
Provides explicit failure handling for error conditions
Status Reporting
Clearly indicates workflow failed for monitoring and logging
Conditional Branching
Can be used in conditional flows to handle failure paths
Configuration Options
Failure Configuration
The End Failure node doesn’t require additional URL or data configuration. It focuses on:
- Immediate Termination: Stops workflow execution instantly
- Failure Status: Marks the entire workflow run as failed
- Error Context: Uses the description to provide failure reason
- Cleanup: Ensures proper cleanup of resources before termination
Example Description:
Node Settings
Terminal Node
Behavior:
- No outgoing connections allowed
- Immediately terminates workflow
- Cannot be bypassed or continued
- Final node in this execution path
Failure Status
Result:
- Workflow marked as failed
- Execution stops immediately
- Error logged with description
- Triggers failure notifications if configured
Use Cases
Authentication Failures
Authentication Failures
Terminate workflow when login attempts fail or authentication is rejected.
Data Validation Errors
Data Validation Errors
End workflow when required data is missing or invalid, preventing incorrect operations.
Timeout Conditions
Timeout Conditions
Stop execution when operations take too long or elements are not found within expected timeframes.
Critical Error States
Critical Error States
Terminate workflow when encountering conditions that make continued execution impossible or dangerous.