async/await common mistakes I keep seeing in production_

If you are writing a library (not application code), always use .ConfigureAwait(false) on every await. This avoids capturing the synchronization context and prevents deadlocks in callers who have not gone fully async yet.

async void methods cannot be awaited, so exceptions thrown inside them crash the process. The only valid use case is event handlers. Use async Task everywhere else. I have personally seen this take down a production service.

Pinning Stephen Cleary's blog series on async as required reading for this thread. It is the definitive guide on not blocking on async code in C#.

The most common async bug I see is calling .Result or .Wait() on a Task inside an async method running on a synchronization context. This deadlocks 100% of the time in ASP.NET Framework and WinForms. Always use await instead.