Sergey Odinokov

.NET Core support for this package wasn't announced yet when Hangfire migrated to .NET Core. And when support for it released I didn't want to put its support back and...

The following APIs were expected to be used to tell application components that application is about to be stopped in the early versions of .NET Core, that's why `UseHangfireServer` method...

Recurring job scheduler behaves the same way as System.Threading.Timers – it doesn't execute jobs in place, it enqueues a new background job when it's time to do so. There's a...

Ah, and `DisableConcurrentExecution` should also be marked with the `ObsoleteAttribute`.

@alphaeleven, what storage are you using and what version of Hangfire.* packages do you have? Also, are you using interfaces for your job (e.g. IHousekeepingService)?

Have you tried to reproduce it when using `Hangfire.Pro.Redis` or `Hangfire.SqlServer` packages instead? The locking feature heavily depends on the implementation of locks inside a storage package. If it's not...

Please try using `IRecurringJobManager` service instead of static `RecurringJob` class and `JobStorage` service instead of static `JobStorage.Current` property (and the same with `IBackgroundJobClient` instead of `BackgroundJob`): ```csharp var backgroundJobs =...

Hangfire can not do anything if a background job method throws this exception. If it ignores it, then application can potentially be in the wrong state. The only correct solution...

Please check the `RecurringJobManager.TriggerExecution` method available from version 1.7.29.

Thanks for noticing that, `TriggerExecution` method will be added to the static `RecurringJob` class in version 1.7.31.