How to implement batch job processing and continuation workflows in Hangfire Pro vs Standard?

Question

Veera Heikkinen · Answer

The key difference is that Hangfire’s standard offering supports continuations between individual jobs, while Hangfire Pro adds a native batch API for grouping jobs and continuing after a batch.

Hangfire Pro: fan out, then continue

Use a batch when several independent jobs should be created together and a later step should wait for that group:

using Hangfire;
using Hangfire.Pro;

var batchId = BatchJob.StartNew(batch =>
{
    // Add independent work items to the same batch.
    batch.Enqueue(() => ImportPart(1));
    batch.Enqueue(() => ImportPart(2));
});

// Schedule follow-up work against the batch, not just one child job.
BatchJob.ContinueBatchWith(batchId, batch =>
{
    batch.Enqueue(() => FinalizeImport());
});

The child jobs can run in parallel, subject to available workers, and their execution order is not guaranteed. A batch continuation is the useful fan-in point: it lets you express that later work depends on the batch as a whole. Check the continuation options for your Hangfire Pro version if the follow-up should run under conditions other than the default success behavior.

Standard Hangfire: continuations are per job

Core Hangfire provides BackgroundJob.ContinueJobWith, which attaches a continuation to one parent job:

using Hangfire;

var importJobId = BackgroundJob.Enqueue(() => ImportPart(1));

// This continuation depends on this job, not on a group of jobs.
BackgroundJob.ContinueJobWith(
    importJobId,
    () => FinalizeImport());

If you enqueue several jobs in Standard, attaching a continuation to one of them does not make it wait for the others. There is no native batch-level continuation or batch creation API in the standard offering.

Choosing between them

Use Pro for native batch creation and a continuation that represents the whole group. This is the simpler fit for fan-out/fan-in workflows.
Use Standard when each job can have its own continuation, or when you are willing to implement the join yourself. A common approach is to track child completion in persistent storage and enqueue the final job once all expected children have reported completion. Make that tracking update atomic or idempotent so retries do not trigger the final step early or more than once.

In short, standard Hangfire has individual job continuations; Hangfire Pro adds the batch abstraction. Choose based on whether you need a genuine “after all these jobs” workflow, rather than just a follow-up to one job.

How to implement batch job processing and continuation workflows in Hangfire Pro vs Standard?

Chaining Jobs in Hangfire

Single Job Continuation Example

1 Answers

Hangfire Pro: fan out, then continue

Standard Hangfire: continuations are per job

Choosing between them

forum

How to implement batch job processing and continuation workflows in Hangfire Pro vs Standard?

Chaining Jobs in Hangfire

Single Job Continuation Example

Can you answer this question?

1 Answers

Hangfire Pro: fan out, then continue

Standard Hangfire: continuations are per job

Choosing between them