Hi, there is a reference to a new library(?) "arrow-resilience".. this will be a separate dependency, right ? https://arrow-kt.io/learn/resilience/retry-and-repeat/#repeating-an-action When I use any function from resilience (Schedule.repeat for example), a "suspend" context is required. When the functionality I want to protect by resilience is non-suspend ("eager" is the wording in arrow ?), can I use the resilience API also in an eager context ? Is wrapping the blocking functionality in a "runBlocking" recommended ?

Hmm 🤔 The only reason this is

suspend

is so that we can allow

suspend

functions inside

log

,

doUntil

, etc. Schedule doesn't actually use any suspension inside, so if your Schedule is suspension free and your code inside

retry

or

repeat

is suspension free than using

runBlocking

will not actually block IIRC.