Async await cancelations during Send

[mwpowellhtx]

I was noticing that during a WPF dispatch timer (Tick) event, I did an IMessenger.Send<T>, and during that, my IRecipient<T>.Receive(T) function was async await. In theory that is an implementation detail, and for reasons, the stuff I was doing, is necessarily also async so need to await. It's not long lived enough to justify a background or worker thread, so messaging makes sense...

public virtual async void Receive(MyMessage message)
{
    await ... ; // Was showing evidence of cancellation
}

But what I soon discovered, the operation was encountering a canceled state, probably wrapped by an AggregateException as well. My workaround, at the moment, was to factor the async await stuff to a different method, and to:

private async Task DoStuff(...) { }
// ...
Task.Run(async () => await DoStuff(...)).Wait();

Which seems to work, which I think is probably affording a non-canceling token.

First, though, I wondered if others have encountered a similar such behavior, canceled operations during async await methods, and identified some plausible workarounds.

Second, is it okay from the sender perspective, I think, to send during the DispatchTimer.Tick. I have a Semaphore guarding the timer being invoked, because I do not want to pile up overlapping messaging requests, obviously, and it is okay if perhaps we miss one or two during the current response.

Ideally, I'd like to kick off something Task oriented and have them all be running together, if possible. But for the async await cancelation issue.

Secondary to all that is, during the DispatchTimer.Tick, which was blocking the UI thread. But I think I have that sorted out by virtue of
DispatcherPriority.ApplicationIdle.

But if there are any other or better insights, I am open to considering what those might be.