I’m testing a proof of concept with sql server and redis hangfire servers running in the same service, as we want to try and accelerate some of our jobs that at less important (while the important ones stay in sql server).
We have JobStorage.Current set up as sql server, because IThrottlingManager cannot be resolved without JobStorage.Current being set (another issue), however I’ve noticed today that executing any action from the sql server dashboard works, and the redis dashboard returns a 500 internal server error.
Digging into the stack traces, when you execute an action from the redis dashboard, it appears to try executing this on JobStorage.Current, even though it was passed it’s own RedisStorage object on setup.
AppPath = null,
Authorization = new
IgnoreAntiforgeryToken = true