Hangfire Integration

Use this package to propagate the current tenant context into Hangfire background jobs. When a job is enqueued during an active tenant request, the tenant ID is stored as a job parameter. When the job executes on a Hangfire worker, the tenant scope is restored so that any code running inside the job sees the correct ITenantContext<TKey>.

What Tenantry.Pro.Hangfire ProvidesCopy Anchor Link

• TenantJobFilter<TKey> — Hangfire IClientFilter + IServerFilter that captures and restores the tenant context
• pro.AddHangfireTenantFilter() — registers the filter in DI
• app.UseTenantryHangfire<TKey>() — adds the filter to Hangfire's GlobalJobFilters

RequirementsCopy Anchor Link

• Tenantry.Pro.Hangfire NuGet package
• Hangfire 1.8+

RegistrationCopy Anchor Link

using Tenantry.Pro;
using Tenantry.Pro.Hangfire.Extensions;

// 1. Register DI services
builder.Services.AddTenantry<string>(tenant =>
{
    tenant.ResolveFromHeader("X-Tenant-Id");
    tenant.UseStore<MyTenantStore>();
    tenant.UsePro(pro =>
    {
        pro.WithLicence(builder.Configuration["Tenantry:Licence"]!);
        pro.AddHangfireTenantFilter();   // registers TenantJobFilter<TKey> in DI
    });
});

// 2. Configure Hangfire (your transport of choice)
builder.Services.AddHangfire(config => config.UseMemoryStorage());
builder.Services.AddHangfireServer();

var app = builder.Build();

// 3. Wire the filter into Hangfire's GlobalJobFilters
app.UseTenantryHangfire<string>();

app.UseHangfireDashboard();
app.Run();

BehaviourCopy Anchor Link

Missing-tenant policyCopy Anchor Link

When a job has no resolvable tenant — none was stamped, the stamped value can't be parsed as TKey, or the tenant isn't in the store — AddHangfireTenantFilter decides what to do via TenantPropagationOptions.OnMissingTenant:

pro.AddHangfireTenantFilter(o => o.OnMissingTenant = MissingTenantBehavior.Skip);

Use Allow for deployments with legitimately global jobs; use Reject/Skip to make an unexpectedly-untenanted job fail loudly or drop rather than run cross-tenant. The same option exists on every Tenantry.Pro integration (MassTransit, Quartz, Rebus) and mirrors core's EfCoreIsolationOptions.OnMissingTenant.

Accessing the tenant inside a jobCopy Anchor Link

public class ReportJob(ITenantContext<string> tenantContext)
{
    public void Execute()
    {
        // tenantContext.CurrentTenantId is set to the tenant that enqueued the job
        var id = tenantContext.CurrentTenantId;
    }
}

LimitationsCopy Anchor Link

• Hangfire server filters are synchronous. The tenant store lookup uses .GetAwaiter().GetResult(), which blocks the Hangfire worker thread briefly. This is acceptable because Hangfire workers run on background threads, not on ASP.NET request threads.
• Jobs enqueued outside a tenant scope (e.g. from admin background tasks) execute without a scope. Inject ITenantContext<TKey> and check HasTenant if your job must handle both cases.