Healthie.NET.Hangfire 4.1.0

Prefix Reserved
dotnet add package Healthie.NET.Hangfire --version 4.1.0
                    
NuGet\Install-Package Healthie.NET.Hangfire -Version 4.1.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Healthie.NET.Hangfire" Version="4.1.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Healthie.NET.Hangfire" Version="4.1.0" />
                    
Directory.Packages.props
<PackageReference Include="Healthie.NET.Hangfire" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Healthie.NET.Hangfire --version 4.1.0
                    
#r "nuget: Healthie.NET.Hangfire, 4.1.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Healthie.NET.Hangfire@4.1.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Healthie.NET.Hangfire&version=4.1.0
                    
Install as a Cake Addin
#tool nuget:?package=Healthie.NET.Hangfire&version=4.1.0
                    
Install as a Cake Tool

Healthie.NET - Trust your uptime

Healthie.NET.Hangfire

NuGet

Live demo — healthie.compiletheory.com — a read-only Healthie.NET dashboard watching real status pages (Anthropic, OpenAI, GitHub, Cloudflare, and more), built from these packages.

Hangfire IPulseScheduler implementation for Healthie.NET. Schedules each pulse checker as a Hangfire recurring job.

Installation

dotnet add package Healthie.NET.Hangfire

Usage

Configure Hangfire as you normally would, then add one line:

using Healthie.Scheduling.Hangfire;

builder.Services.AddHangfire(c => c.UseSqlServerStorage(connectionString));
builder.Services.AddHangfireServer();

builder.Services
    .AddHealthie(typeof(Program).Assembly)
    .AddHealthieHangfire();

Hangfire's storage, retry policy and dashboard stay yours to configure — a library that picked them would be picking where your job data lives.

What it buys you

The schedule lives in storage rather than in the process, so it survives a restart. And across several replicas each occurrence is handed to exactly one server, so a scaled-out deployment runs each check once rather than once per replica — which the built-in timer does not do.

Recurring jobs appear in the Hangfire dashboard under the healthie: prefix, alongside their run history.

Granularity

Hangfire notices due work by polling, every 15 seconds by default, so a check asking to run more often than that will not. Lower BackgroundJobServerOptions.SchedulePollingInterval, or keep the fast checks on the built-in timer.

Hangfire schedules only by cron, so a fixed period has to become a cron expression. Periods that divide evenly into a minute, an hour or a day convert; seven seconds does not, and is refused rather than approximated — a cron expression firing at :00, :07 … :56 would wait four seconds before starting the next minute. Give such a checker a cron expression of its own instead.

Cron expressions pass through untouched: Hangfire parses cron with Cronos, the same standard Unix syntax Healthie.NET uses.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.1.0 34 7/30/2026
4.0.0 37 7/30/2026

Twenty packages was too many, and two of them had no business being separate. This release fixes
that without breaking anything: **an application on 4.0.0 upgrades by changing nothing.**

### Added

- **`Healthie.NET`**, the package to install first. It carries no code of its own, only a dependency
 on `Healthie.NET.DependencyInjection`, so it is one install and one dependency rather than a
 bundle -- no provider, scheduler or UI framework arrives with it. The name people guess did not
 exist before, and the actual entry point was called `DependencyInjection`, which reads like
 plumbing rather than the way in.
- **Uptime reporting and leader election are in the core package.** `AddHealthieUptime()` and
 `AddHealthieLeaderElection()` need nothing else installed. Both stay opt-in: nothing runs until
 you call them.

### Deprecated

- **`Healthie.NET.Uptime`** and **`Healthie.NET.LeaderElection`**. Neither carried a third-party
 dependency, so keeping them separate cost two installs and saved nothing -- the provider packages
 exist to keep Npgsql or Temporalio off machines that do not use them, and these two were not
 providers.

 **Nothing breaks.** Both packages are still published, now as assemblies of type forwards, so an
 application that references either keeps compiling *and* keeps running untouched. That is what
 makes this a minor release: moving a type between assemblies is a binary break the compiler cannot
 see, because source keeps building and only the runtime finds out. Remove the reference whenever it
 suits you; neither package will gain features.

### Fixed

- **The sample Dockerfiles took their .NET base images by mutable tag.** A tag is a different image
 next week, so the build that passed review is not the build that ships. Both are pinned by digest,
 which Dependabot updates the way it updates a package version. Closes four OpenSSF Scorecard
 *Pinned-Dependencies* findings.

### Security

- **An Azure CosmosDB key committed in May 2025 was confirmed dead and the alert closed.** It had
 already been removed from the working tree; the account it belonged to no longer exists in the
 owning tenant, verified by enumerating every Cosmos account across that tenant's subscriptions, so
 the key authenticates to nothing. It remains in history at `ee0c78e`, inert.
- **Stray screenshots can no longer be committed.** Root-level PNGs are ignored, scoped to the root
 so the images the docs and samples genuinely ship are untouched.

Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v4.1.0/CHANGELOG.md