Error handling and recovery
Exception caught and dropped
A catch block logs nothing and returns a default, so a failed write looks like success to the user and to the team.
Termsfault injection (making a dependency fail on purpose in staging to see what the user and the logs show) · API (the interface other software calls; tested directly, without the UI in between) · webhook (a message a provider such as Stripe sends to your server when something happens, like a payment)
highseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
CodeRabbit measured error-handling gaps nearly 2 times more common in AI-co-authored pull requests over 470 open-source pull requests.
In the same 470-pull-request sample, cross-site scripting issues were up to 2.74 times more frequent in AI-co-authored pull requests; error-handling gaps were nearly 2 times more common and logic and correctness issues 75% more common.
Source: CodeRabbit, 2025-12-17 · verified 2026-09-21
How we detect it
Force each backing call to fail and look for a user message and a log entry.
Checklist items that catch it
Failures surface to the user and to logs
automated Force a failure in each critical flow's backing call (database, payment, email, model).
The user sees a specific message and a log entry with a request id exists for every forced failure.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in error handling and recovery
- medium
- medium
- medium
- medium
- medium
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.