Anyone had any luck with

tryExecuteAndNotify

and your own controller returning an error message that shows up as a notification bottom right?

@Warren Buckley I've been hitting the same issue, it would be nice if tryExecuteAndNotify would show the error if it was just a 400 (or any other error-isch code) with a string in the body. I ended up using the built-in ProblemDetailsBuilder in a controller base class when returning errors. Similar to this

var problemDetails = new ProblemDetailsBuilder()
    .WithTitle("Error")
    .WithDetail(errorBody.Message)
    .Build();
return StatusCode(400,problemDetails);