Extension library to add custom queue logic
This library will create and use the destination database on first usage. Only MSSQL database supported.
Be sure to provide correct connectionstring with all required user rights to maintain the database (create, read, upsert, delete).
SQL_CONNECTIONSTRING - connectionstring to the database WITHOUT database name parameter
HANGFIRE_SCHEMA - hangfire schema name
HANGFIRE_DATABASE - hangfire database name
HANGFIRE_JOB_TABLE - Hangfire job table where the job identifiers will be stored.
This library is using the queue named handler - it needs to be inserted into the Hangfire queue settings.
Out of the box, Hangfire method ContinueJobWith() doesn't apply to Failed jobs
- decorating the background job method with this attribute allows to extend the
ContinueJobWithexecution also toFailedjobs so they will be also removed from the handler job table and not blocking incoming jobs with same identifier.
There might be issue when your jobs won't be cleared properly. This happen when your application was closed unexpectedly (for example server error or unhandled application error). Hangfire might not create some job parts, so the continuation of the job will fail to find correct state of the job and just not be fired - So your job queue entry won't be processed at all. To deal with this situation, there is both method CleanupHangingTasks() that you can add as recurring job (or wherever you like) and HangfireJobHandlerStartupService Hosted Service that can be added to startup configuration to run cleanup task every 1 hour in case of hanging jobs.