Hangfire.Pro 2.3.2

https://www.hangfire.io/blog/ 2.3.2 * Fixed – Possible external state changes for jobs in batch continuations should not lead to stuck batches. 2.3.1 * Fixed – Add missing overloads for the `ContinueBatchWith` method to support async jobs for `netstandard` targets. 2.3.0 * Added – It is possible to use `OnlyOnCompletedState` and `OnlyOnDeletedState` options for batch continuations. * Added – Make it possible to specify multiple `BatchContinuationOptions` for batch-to-batch continuations. * Added – Allow to specify multiple `BatchContinuationOptions` for batch-to-job continuations. * Added – Allow to use multiple `JobContinuationOptions` values for job-to-batch continuations. * Added – Show job continuations on the "Batch Details" page in Dashboard UI. * Changed – `BatchContinuationOptions` enum is now decorated with the `FlagsAttribute` attribute. 2.2.3 * Changed – Order of the `BatchSupport` filter was changed from 2000 to 950 to fire earlier than `ContinuationsSupport`. * Fixed – Continuations hanging in the `Awaiting` state when antecedent background job belong to a canceled batch. 2.2.2 * Added – Allow to configure maximum number of entries for final state lists. * Fixed – Use LazyThreadSafetyMode.PublicationOnly to avoid caching "JobStorage.Current is null" exceptions. * Fixed – JsonSerializationException: Unable to find a constructor to use for type Hangfire.Batches.AwaitingBatchState. 2.2.1 * Fixed – Occasional timeout exceptions when attaching nested batch continuations. 2.2.0 * Added – Separate target for .NET Standard 2.0 to reduce the number of dependencies. * Added – `ContinueJobWith` and `ContinueBatchWith` methods to replace `AwaitXXX` ones and match Hangfire 1.7. * Fixed – Avoid constant exception in some corner cases related to batch and job continuations. 2.1.2 * Fixed – Leaks in the `Set` table when cancelling a batch that has continuations for its jobs. * Fixed – Continuation stuck in a non-initialized state, when parent batch of antecedent item is canceled. 2.1.1 * Fixed – Possible race condition in the `UseBatches` method that may lead to the 'Batches are not initialized' exception. 2.1.0 * Added – Full support for job and batch continuations in nested batches. * Fixed – Continuations now work properly, when antecedent job/batch and continuation have the same batch. 2.0.1 * Fixed – Background job or batch may appear in different sets at the same time, preventing a batch from completion. 2.0.0 * Added – .NET Core support via the `netstandard1.3` target. * Added – Ability to change batch expiration time using the `UseBatches` method. * Added – Support for nested batches, whose completion is required for parent ones. * Added – Ability to add a batch continuation for job and job continuation for batch. * Added – Possibility to attach jobs and batches to an already existing batch. * Added – Support for lazy cancellation of a batch, without iterating through all the jobs. 1.4.10 * Fixed – Throw an exception, when can't change the state of a continuation. * Fixed – Fix race condition that leads to forever waiting batch continuations. 1.4.9 * Fixed – CreatedAt timestamps for statese now written just before serializing. * Fixed – Regression in 1.4.8, final state is now shown correctly in dashboard. 1.4.8 * Fixed – Batches were hanging indefinitely in a started state, when using continuations for finished jobs. * Fixed – Batches are always created in a correct state, even if its jobs were already finished. * Fixed – "continuation" set key now correctly expiring, when parent batch already finished. * Fixed – Don't serialize immutable properties of a batch state. * Fixed – Add more descriptive messages for continuation state change reasons. * Fixed – Do not expire empty "pending" and "processing" sets on final state transitions. 1.4.6 * Changed – Remove redundant distributed lock acquisition, when executing continuations. * Fixed – Increase batch lock timeouts when adding a batch continuation. * Fixed – Batches are now controlling expiration time of their background jobs. * Fixed – Increase batch filter's order value to disallow custom job filters to override job expiration time. 1.4.4 * Fixed – Background jobs of a batch continuation may expire before the continuation fires. 1.4.3 * Fixed – "Could not find type Hangfire.Batches.BatchAwaitingState" exception (full fix). 1.4.1 * Fixed – "Could not find type Hangfire.Batches.BatchAwaitingState" exception (fixed partly). 1.4.0 * Added – Ability to pass custom IJobFilterProvider for batched jobs. * Changed – Hangfire.Pro now requires Hangfire.Core 1.5.0. * Changed – Throw an exception when Configuration.UseBatches method wasn't called. * Changed – Several internal classed made internal, they were public by mistake. * Changed – Removed unnecessary distributed lock acquiring. * Fixed – BatchJobSupportAttribute is now apply state filter to prevent races related to filter order. 1.3.2 * Fixed – Distributed lock TimeoutException with batches when using SQL Server. 1.3.1 * Changed – Optimized `BatchJobSupport` attribute to use less commands in a transaction. * Fixed – Race condition when background jobs disappear from batch continuations. * Fixed – Parent batch URL for a continuation in the Batch Details page now works correctly.