4.2.1. Pipeline Errors and the Fail Activity

💡 First Principle: The Fail activity provides controlled pipeline termination with custom error messages—like a circuit breaker that trips with a clear reason code. Instead of silent failures or generic errors, you get actionable information about what went wrong.

Scenario: A Lookup activity queries reference data that should always exist. If it returns empty, the pipeline should fail with a clear message indicating which reference data is missing.

Fail Activity Configuration

Visual: Fail Activity Pattern

Implementation Pattern

1. Add Lookup activity to query required data
2. Add If Condition to check for empty results
3. Add Fail activity in the True branch
4. Configure error message and code
5. Continue processing in False branch

⚠️ Exam Trap: Logging errors without failing the pipeline allows downstream activities to continue with bad data. If a condition should stop execution, use the Fail activity—logging alone is insufficient.