Flow Basics
Error Shield
This document explains the Error Shield node, which protects your workflow by catching and handling errors.
What It Does
Error Shield works like a protective wrapper around other nodes - if something goes wrong inside, it catches the error instead of letting your workflow crash.
Inputs and Outputs
Inputs
- Wrapped Node: The node you want to protect from errors
- Pass Inputs Through: When enabled, you can access the original input that caused an error
Outputs
Two possible paths:
- Success Path: Data that processed successfully
- Error Path: Triggered when an error occurs
When “Pass Inputs Through” is enabled:
- Success Path: Processed data
- Error Path: The original input that caused the error
Examples
Basic Example
Loop Mode Example
Working with Join Paths
You can use Join Paths to reconnect the success and error paths into a single workflow:
Basic Join Pattern
Example Use Case
By using Join Paths after Error Shield, you can:
- Handle both successful and failed cases
- Continue your workflow with a single path
- Process all results together, regardless of success/failure
Common Use Cases
- Web Scraping: Catch and handle failed website requests
- File Processing: Continue even if some files can’t be processed
Step-by-Step Usage
- Drag Error Shield onto canvas
- Place the node you want to protect inside it
- Enable “Pass Inputs Through” if you need to know which inputs failed
- Connect both success and error paths
- Use Join Paths to reunite the paths if needed
- Add error handling for failed cases