for example if async failed it will cancel parent Job (for non-Supervisor Job)

but on practice such pattern as:

async { }.await()

is always wrong, I don’t see any valid use case for it

Just worried about accidentally blocking.

properly written suspend function shouldn’t block

also you always can use withContext(someDispatcher) { suspendFun } to use different dispatcher to be sure that it will not block your current coroutine

exactly for this use case, repository

So yeah, there is this use case, and it more clean imo than usage of non-cancellable coroutine on the same. But it’s clearly not the case of original question