@pniederw My desired behavior is that the code will run synchronously until it hits an

await()

and then it returns to the calling code, the portion after the

await()

is completed later in another thread when

await()

returns with a value.

future {}

appears to do this, the only problem is that it appears to silently swallow exceptions, which is unacceptable from a debugging perspective.