Error Handling in PowerShell

Overview

Reliable automation requires explicit error handling for cmdlet failures, external command failures, and transient infrastructure conditions.

Error Handling Tools

• try / catch / finally
• -ErrorAction Stop for terminating behavior
• $LASTEXITCODE for native executable results
• Structured logging with context fields

flowchart TD
    A[Execute Step] --> B{Error?}
    B -->|No| C[Next Step]
    B -->|Yes| D[Catch and Log]
    D --> E[Retry or Fail Fast]

Practical Example

try {
    Get-Item -Path .\config.json -ErrorAction Stop
}
catch {
    Write-Error "Configuration file missing: $($_.Exception.Message)"
    exit 1
}

Production Example

Deployment scripts typically retry cloud API calls with exponential backoff before marking pipeline failure.

Common Pitfalls

• Silent failures due to default non-terminating errors
• Catching all exceptions without useful diagnostics
• Retrying permanent errors indefinitely

Key Takeaways

• Strong error handling prevents partial automation failures.
• Terminating behavior should be explicit for critical steps.
• Retries must be bounded and observable.