Sergey Odinokov

Not quite, Hangfire.Autofac doesn't depend on ASP.NET Core at all, that `JobActivator` class is Hangfire.Core's abstraction that doesn't have any references to ASP.NET Core. I think that some other kind...

Hm, just realized that `JobActivator` class is simply not available in the `Worker` class, where a `PerformContext` class is created, and it's treated as an implementation detail of the `CoreBackgroundJobPerformer`...

Good point, @jvmlet! Unfortunately, the activator scope is created after `IServerFilter.OnPerforming` method is already finished and has a very narrow scope, so we can't implement this in the current version.

The goal here is to make it accessible also in IServerFilter implementations, as a property in the PerformContext class to allow them resolving the same services as the background job...

Thanks for all the details. These are the lines where 422 status code is set for the `Trigger` button, so perhaps there are problems with decoding the job identifiers. https://github.com/HangfireIO/Hangfire/blob/d51e2c54dc49b28b3f340bb19d5fdcc394bb1b5d/src/Hangfire.Core/Dashboard/BatchCommandDispatcher.cs#L47-L52...

Unfortunately can't reproduce this, looks like there are problems with reading the form values, since it happens before even going to the job storage in the lines referenced earlier. Can...

Great, so we have a request with `x-www-form-urlencoded` parameters, and an empty `FormCollection` in ASP.NET Core, and `ContentType` property is set to `application/x-www-form-urlencoded; charset=UTF-8`, so there should be no issues....

These are my results: 

Hm, this class comes from the `Microsoft.AspNetCore.WebUtilities` package that uses Source Link to provide source code since version 2.1.0 released in 2018. What .NET version you are using?

Hm, your project is new enough to avoid that problem with source link. My project was based on SDK 8.0.410. What if we include `Microsoft.AspNetCore.WebUtilities` package of its latest version...