Is there a better way to only send a "completion message" on a successful completion of flow when using a cancel? in this case, batchMeetings is my own impl of

flow.chunked()

var caughtException = false
        val batches = batchResults(inputFlow, chunkSizePerMessage)
            .map { createResults(it) }
            .catch {
                caughtException=true
                emit(Results.TerminateWithError(it))
            }
        emitAll(batches)
        if(!caughtException) {
            emit(Results.SuccessfulFinish())
        }

Ideally, the Successful finish would only be sent on no exceptions from the upstream flow. That

var caughtException

seems ugly. Is there a cleaner way?

What's the use-case for that?

The flow emits a sealed class of (data, error, Success(completedAt). So a normal flow would be D1, D2, D3, D4, Complete(timeStamp) and error case D1, D2, D3, Error

error's no problem. But why do you need to handle cancellation?

Wait.. that's it? I had them in the opposite order.. the catch in front on the onCompletion

Yes. You can do

.onCompletion { if (it != null) emit(...) }

.

only input would be onError() and onSuccess(). That's not obvious though still