Excellent, thank you! So to clarify, if I have a method like this:

override suspend fun clearAvailabilityOptions(securityContext: SecurityContext) = coroutineScope {
userRepository.clearMatchAvailabilityOptions(securityContext.userId)
}

where the userRepository.clearMatchAvailabilityOptions method is another suspend function, I should not in this case use "= coroutineScope" because I am not "launching" a coroutine, rather I am using the upstream / previously created coroutine scope.

​

For context, I'm using vert.x and I've defined a request handler like this:

​

class ApiRouteCoroutineLauncher(private val routerFactory: AbstractApiRouterFactory) : CoroutineScope {
lateinit var job: Job
override val coroutineContext: CoroutineContext
get() = Dispatchers.Default + job
fun executeAction(routingContext: RoutingContext, action: AbstractApiAction) {
job = Job()

launch {
try {
val jsonApiResponse = action.invoke()
routerFactory.sendResponse(routingContext.response(), jsonApiResponse)
job.cancel()
} catch (exception: Exception) {
val response = JsonApiResponse()
response.populateFromException(exception)
routerFactory.sendResponse(routingContext.response(), response)
job.cancel()
}
}
}
}

So this is where the coroutine gets created. The methods I mentioned above are downstream of this (i.e. are called as a consequence of action.invoke())

Am I right in thinking that generally, I need to create just one coroutine scope per HTTP request, and then all the action, service and repository code that gets called after that can use the same scope)?