I would catch for a throwable rather than just for...

# coroutines

[Pablichjenkov]

I would catch for a throwable rather than just for io and http exception. Many stuff can go wrong when execution takes place. Better catch for the most general case Throwable and filter later by checking with instance of in a Util Helper class or sort of