Configuring Job Queues

Hangfire can process multiple queues. If you want to prioritize your jobs, or split the processing across your servers (some processes for the archive queue, others for the images queue, etc), you can tell Hangfire about your decisions.

To place a job into a different queue, use the QueueAttribute class on your method:

public void SomeMethod() { }

BackgroundJob.Enqueue(() => SomeMethod());

Queue name argument formatting

The Queue name argument must consist of lowercase letters, digits, underscore, and dash (since 1.7.6) characters only.

To begin processing multiple queues, you need to update your BackgroundJobServer configuration.

var options = new BackgroundJobServerOptions
    Queues = new[] { "alpha", "beta", "default" }

// or
using (new BackgroundJobServer(options)) { /* ... */ }

Processing order

Queues are run in the order that depends on the concrete storage implementation. For example, when we are using Hangfire.SqlServer the order is defined by alphanumeric order and array index is ignored. When using Hangfire.Pro.Redis package, array index is important and queues with a lower index will be processed first.

The example above shows a generic approach, where workers will fetch jobs from the alpha queue first, beta second, and then from the default queue, regardless of an implementation.


For ASP.NET Core, define the queues array with services.AddHangfireServer in Startup.cs:

public void ConfigureServices(IServiceCollection services)
    // Add the processing server as IHostedService
    services.AddHangfireServer(options =>
        options.Queues = new[] { "alpha", "beta", "default" };