I have 3 Tasks that should run in parallel. I need to await all 3 and then continue processing their results. So something like:
var results = await Task.WhenAll(task1, task2, task3);
return process(results);
This works fine when all 3 tasks complete successfully. However, if one of them fails I get an exception that bubbles up all the way. This is not what I want. If any of these tasks throws an InvalidOperationException
I can continue processing, I just need the process
method to have access to the exception that was thrown.
I realize that I can try...catch
within the tasks but that does not seem like it would be a hack. Beyond being semantically incorrect (the task DID fail - it should not return successfully), if I went with this approach, since the result can be successful OR return an exception, I would have to return a custom type. The Task<T>
object however already exposes an Exception channel so I would prefer to not do double-duty and just use what is already present.
You can handle this case like in my example below:
Task<T>[] tasks = new Task<T>[] { task1, task2, task3 };
try
{
await Task.WhenAll(tasks);
}
catch(InvalidOperationException exception) // If you need to handle any other exception do it
{
// handle it if you wan to
}
// You can use task1.IsFauled to know if current task failed,
// and you can use task1.Exception to know why it failed
return process(tasks.Where(t => !t.IsFauled).ToArray());
If I understand you correctly, you're looking for this?
var tasks = new[] { task1, task2, task3 };
try { await Task.WhenAll(tasks); } catch (...) { }
return process(tasks);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With