Healthie.NET.Hangfire
4.1.1
Prefix Reserved
dotnet add package Healthie.NET.Hangfire --version 4.1.1
NuGet\Install-Package Healthie.NET.Hangfire -Version 4.1.1
<PackageReference Include="Healthie.NET.Hangfire" Version="4.1.1" />
<PackageVersion Include="Healthie.NET.Hangfire" Version="4.1.1" />
<PackageReference Include="Healthie.NET.Hangfire" />
paket add Healthie.NET.Hangfire --version 4.1.1
#r "nuget: Healthie.NET.Hangfire, 4.1.1"
#:package Healthie.NET.Hangfire@4.1.1
#addin nuget:?package=Healthie.NET.Hangfire&version=4.1.1
#tool nuget:?package=Healthie.NET.Hangfire&version=4.1.1

Healthie.NET.Hangfire
▶ Live demo — board.healthie-dotnet.dev — a read-only Healthie.NET dashboard watching real status pages (Anthropic, OpenAI, GitHub, Cloudflare, and more), built from these packages. Full documentation at healthie-dotnet.dev.
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 | Versions 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. |
-
net10.0
- Hangfire.Core (>= 1.8.24)
- Healthie.NET.Abstractions (>= 4.1.1)
- Newtonsoft.Json (>= 13.0.4)
-
net8.0
- Hangfire.Core (>= 1.8.24)
- Healthie.NET.Abstractions (>= 4.1.1)
- Newtonsoft.Json (>= 13.0.4)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Fixed
- **The dashboard cropped its own rows on anything narrower than a laptop.** The row and its column
header share one track definition, and two rules overrode it: a read-only board drops the controls
column, and a narrow viewport folds the row down to three. Written as separate rule sets they
fought on specificity, and `.hpm-list--readonly .hpm-row` outranks a `.hpm-row` inside a media
query -- so on a read-only board the fold never applied at any width. Every row was drawn with
five tracks demanding 556px inside a 342px phone: 214px of columns clipped off the right, the name
squeezed to its 160px minimum to make room for columns that were not visible anyway, and no
scrollbar to reach them, because the overflow was clipped rather than scrolled. The definition is
now a single custom property on the list, which is the one element both variants already sit on,
so the fold cannot be outranked.
- **The last column was clipped on an ordinary 1280 laptop, read-only or not.** The detail panel
moved below the list at 1100px, but a full row needs a 706px column and the list only reaches that
at 1402px of viewport -- so between those two the three columns fitted the window while the middle
one no longer fitted a row. That threshold is now 1400px, calibrated on the editable board, which
is the wider of the two and the default.
- **Group and tag chips were sliced down the middle on a phone.** They sit on the row's sub-line,
which truncates with `text-overflow: ellipsis` -- and that ellipsizes text, not an inline-flex
pill, so a chip was cut mid-shape instead. The folded row has vertical room the wide one does not,
so the line now wraps there, exactly as it already does on a card.
- **Cards lost their rate, sparkline and last-checked time on a phone.** The three cells were hidden
for every layout below 820px, but only the row layout was short of width; a card stacks them into
areas down its own length, where they fit. They are now hidden for the row layout alone.
### Changed
- **The packages point at [healthie-dotnet.dev](https://healthie-dotnet.dev/).** `PackageProjectUrl`
is the landing site rather than the repository, because NuGet renders it as the package's "Project
website" and a reader who clicks it wants documentation and the live board, not a source tree.
`RepositoryUrl` still points at GitHub, so Source Link and NuGet's own source link are unaffected.
Every package README now links the documentation site alongside the live demo, which moved to
[board.healthie-dotnet.dev](https://board.healthie-dotnet.dev/).
- **Releases carry build provenance.** The release workflow attests which workflow, at which commit,
produced each package, so `gh attestation verify <package>.nupkg --repo ivanvyd/Healthie.NET`
proves a download came from this repository. The SBOM already said what went into a package; this
says who built it, which is the half a tampered build would otherwise be free to restate.
- The repository README leads with a screenshot rather than a 10MB animation, and `Healthie.NET.Redis`
gained the header every other package README already had.
Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v4.1.1/CHANGELOG.md