hangfire-job

Create a scoped job class with an async Task method, register it in DI, then call RecurringJob.AddOrUpdate with a unique job ID, the method expression, and a cron expression such as Cron.Daily(hour: 8). Register recurring jobs after the host is built in Program.cs.

Inject IBackgroundJobClient into the handler and call Enqueue with an expression like j => j.GenerateAsync(invoiceId, tenantId, CancellationToken.None) after the transaction commits. This keeps the HTTP response unblocked while the job runs asynchronously.

Yes, configure it with UseSqlServerStorage passing your connection string and SqlServerStorageOptions. Recommended settings include a dedicated hangfire schema, sliding invisibility timeout of five minutes, and DisableGlobalLocks enabled.

Async void methods cannot be tracked or retried by Hangfire, so failures are silently lost. Job methods must return Task and accept a CancellationToken with a default value so Hangfire can manage cancellation and retries correctly.

Design jobs so running them multiple times produces no duplicate effects, such as marking records as processed after handling them. Add AutomaticRetry with explicit attempts and delays, and log individual item errors without aborting the entire job.