I see now what you mean. Problem of your case, that this Java API doesn't support asyncronous supplier, it have to be syncronous.

I was afraid that might be the case. Is

runBlocking

safe to use? https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/run-blocking.html

Also, I'm not sure that it will work for you real case, but you can first request for value from suspend function and when it will be ready subscribe on get and pass value that you already received asyncronously But it, of course, changes semantics of code, it's not so lazy as could be with asyncronous supplier support

The way the description is written just makes it sound like you shouldn’t be using it for production like activities.

Yes, usually you shouldn't use it, but it's a bridge that allows convert asyncronous coroutine to syncronous code

Thanks again for all the help.

Yes, if you have access to Java code and can change it, I would just convert supplier to some CompletableFeature or other asynchronous primitive that can be used on java side and than you can easily use coroutines (see for example

future

coroutines builder, that crwates ConpletableFuture from suspend block)