Sergey Odinokov

I have fixes this by always throwing an exception, and also using [trace flag 460](https://www.brentozar.com/archive/2019/03/how-to-fix-the-error-string-or-binary-data-would-be-truncated/) on modern SQL Servers to include what actual value has been truncated.

Thanks for the BTW, this bug will be fixed in 1.8.14 that will be released very soon.

There is the hidden [`Hangfire.Common.JobFilterProviders.Providers`](https://github.com/HangfireIO/Hangfire/blob/d92287faf2795e751faca818ffa7cd92b3a12b69/src/Hangfire.Core/Common/JobFilterProviders.cs#L22) property you can use to add a custom filter provider that is based on DI. However I agree, that dependency injection should be tightly integrated...

Starting from Hangfire 1.7.0 it's possible to use the `IServiceProvider` instance when calling the `AddHangfire` method during the configuration: ```csharp services.AddHangfire((provider, configuration) => configuration .UseServiceProviderJobFilterProvider(provider) .UseXXX() .UseZZZ() .UseYYYStorage()); ``` So...

@MiroslavGrozdanovski please give an example of a custom filter that will not work with the `UseServiceProviderJobFilterProvider` extension method, but will work with your `AddScoped` suggestion.

> P.S. The only thing is, you cannot use BackgroundJob / RecurringJob static methods anymore, because they use a private (non-DI) instance of client class, hence they will ignore the...

All feature requests already implemented :smile:: ``` csharp [DisableConcurrentExecution] public void SomeMethod() { /* ... */ } ```

Not yet, but you can look at the [implementation](https://github.com/HangfireIO/Hangfire/blob/master/src/Hangfire.Core/DisableConcurrentExecutionAttribute.cs) and easily build what you want.

Awesome contribution, @stevetsang! But it contains breaking changes to the public `IMonitoringApi` interface. If I merge this PR, a lot of projects must be updated (including all the storages listed...

@fiidim can you post here your settings related to Hangfire and Hangfire.SqlServer?