We experience the following issue after we upgraded our Hangfire versions to 1.8.11: jobs never leave the Processing state, even though the C# code that the job itself executes has finished. We use Hangfire in combination with Hangfire.DynamicJobs to use a single SQL Server database with multiple servers, which we upgraded to 0.2.0 together with the 1.8.11 upgrade of the main Hangfire packages.
We experience the following issue after we upgraded our Hangfire versions to 1.8.11: jobs never leave the Processing state, even though the C# code that the job itself executes has finished. We use Hangfire in combination with Hangfire.DynamicJobs to use a single SQL Server database with multiple servers, which we upgraded to 0.2.0 together with the 1.8.11 upgrade of the main Hangfire packages.