ASP.NET Core async iactionresult
This code is pointless since it creates async state machine while the code you execute is actually synchronous code.
So eventually you get a performance penalty for the creation of a state machine but no reward of asynchronous execution.
Consider using async and await when you're dealing with IO operations. Usually, such methods already provide asynchronous API. You can spot this as such methods return Task or Task&lt;T&gt;