Why this matters
The bug. Catching Exception and doing nothing is the most expensive line of code in many .NET codebases. It hides bugs, slows debugging, and corrupts data — callers expecting an Order get null and fall into bizarre paths.
The fix. Catch the *specific* exception you can handle (HttpRequestException), log it, and either rethrow or return a properly-typed Result<Order, Error>. *Never* silently return null from a catch.
Lint. Roslyn analyzers CA1031 (don't catch general types) and CA2200 (rethrow correctly) catch this.
Review heuristic
Every catch block should answer two questions in the diff or in a comment: which specific exceptions am I handling, and what do I do with the rest? catch (e) {} is the smoking gun; except: pass is its Python cousin.
External reference: CWE-248: Uncaught Exception.