NServiceBus 6+ behavior to run the incoming message

TaskRunBehavior.cs

// If all handlers are compute bound or IO isn't happening early it can result in less concurrent processing as depending on the
// transport and it being full async and no IO is happening message processing could be sequential. This behavior will immediately
// do a Task.Run
//
// Usage:
//         endpointConfiguration.Pipeline.Register(new TaskRunBehavior(), nameof(TaskRunBehavior));
//
class TaskRunBehavior : IBehavior<IIncomingPhysicalMessageContext, IIncomingPhysicalMessageContext>
{
    public Task Invoke(IIncomingPhysicalMessageContext context, Func<IIncomingPhysicalMessageContext, Task> next)
    {
        return Task.Run(() => next(context), context.CancellationToken);
    }
}