error-recovery-patterns

Handle transient network timeouts by implementing retry patterns with exponential backoff and defined retry limits, typically up to three attempts before triggering a fallback strategy to ensure task completion.

Recover from compilation errors by systematically reading the error message, fixing the identified syntax or type issues, and re-running the compilation check to verify the resolution.

Error classification helps in troubleshooting by differentiating between critical, non-critical, and transient errors, which defines specific resolution paths and prevents unnecessary task aborts.

When tool failures occur, apply fallback strategies such as switching to alternative tools, implementing graceful degradation, or skipping non-critical steps to maintain task progression.

Use exponential backoff for error recovery specifically when addressing transient failures, applying defined retry limits to prevent indefinite loops and ensure eventual task completion.

Resolve browser testing failures without stopping execution by classifying them as non-critical if appropriate, applying targeted recovery strategies, or skipping the affected steps gracefully.