When you migrated networking to async/await, what issue only showed up under load?

A common pitfall when migrating networking code to async/await is assuming it automatically enables parallelism. In reality, code may still run on a single executor, causing requests to stack under load without obvious errors. The fix is making concurrency explicit using task groups, where you deliberately define where parallel work happens.