output-error-try-catch

Retries fail when step calls are wrapped in try-catch blocks that swallow errors and disable the Output SDK retry logic. Removing these catch blocks restores the configured retry policies for each step.

Fix try-catch anti-patterns by removing catch blocks around step calls and relying on per-step retry policies. This preserves error context and ensures the Output SDK triggers retries automatically on failure.

Yes, safe fallback patterns exist that provide optional values without bypassing retries. Instead of swallowing exceptions with try-catch, apply per-step retry policies to handle failures while preserving error context.

No, removing catch blocks preserves error context rather than losing it. The Output SDK captures the original error details and applies the configured per-step retry policies to ensure failures are retried correctly.

Avoid try-catch around step calls when you rely on Output SDK retry logic. If errors are swallowed or misclassified by the catch block, retries will not trigger, making try-catch an anti-pattern for standard step execution.