Sergey Odinokov

I think we should ask @unionthugface for details, maybe some options aren't required there.

Hm, do you have any deadlock graphs or at least resource names for these locks available? Also, what version of Hangfire.Core and Hangfire.SqlServer you are using? I haven't seen deadlocks...

Currently, recurring job scheduler will schedule a new job regardless of the processing status of previous job. Consider you have an option that the scheduler enqueues new job only on...

@jacobneroth, consider you can specify the retry intervals on your recurring job that is being executed daily: ``` csharp [AutomaticRetry(Attempts = 3, Intervals = "1200")] // Intervals in seconds separated...

+1 for `Enable` & `Disable` buttons in Dashboard for recurring jobs and corresponding methods in API – this is pretty simple. This feature should be implemented after #158, #160, #167...

Actually there's no any reasonable limits, an Hangfire will slowly enqueue all of them, so everything depends on a storage. However, in recent 1.8.12 version I have added the `MaxDegreeOfParallelismForSchedulers`...

Hello @fairking! The feature is really nice and looks awesome, but it can't be merged with Hangfire, because of breaking changes. A lot of packages, storages depend on this API,...

So what happens with the network on that instance? I'm unsure whether it helps, if I add an immediate retry logic in case of an exception to the Hangfire code...

A lot of changes required for the whole set of libraries to make this change, since these versions aren't backward compatible. Sooner or later, this will be done, but currently...

While I agree that `AsyncLocal` instances shouldn't be preserved across different background job runs, and `ExecutionContext` should be somehow flushed, but this is potentially a breaking change for those who...