We have an ASP.NET MVC 4 application that leverages Hangfire. The applicaition has a dashboard with a grid of application specific background jobs that are long running one time jobs, queued by the user, with no retry functionality. Each row presents the users with the current state of the job, submitted(enqued)/processing/successful/failed. The user is also presented with a delete button for each job. Is there any way via the Hangfire API to kill/abort a background job while it is in the submitted or processing state when the delete button is clicked? If there isn’t can you provide code snippets of how to achieve this and suggest some best practices when implementing it with Hangfire so that we can try to avoid architectural mistakes. Also we are using MS SQL Server.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Long-Running jobs | 0 | 1035 | November 5, 2021 | |
| Unable to cancel whole Hangfire Cancellation process | 0 | 1345 | October 19, 2015 | |
| Background Job Aborted and server stopped working | 0 | 456 | January 22, 2023 | |
| Stopping a job from dashboard | 0 | 985 | October 6, 2021 | |
| Hangifre stops executing jobs after I delete a job | 1 | 1694 | September 23, 2016 |