All 15 Background Services questions
More in Background Services
What is a BackgroundService in ASP.NET Core, and what does it provide out of the box? What is the difference between IHostedService and BackgroundService, and when would you implement IHostedService directly? How does graceful shutdown work for a BackgroundService, and what role does CancellationToken play? How does a BackgroundService differ from a Worker Service project template, and how do they relate? How do you register and run multiple independent BackgroundServices within the same application? How would you implement a scheduled (cron-like) background job in .NET without a third-party library? What is the significance of the order of AddHostedService registrations relative to StartAsync execution, and can you control it? How should a BackgroundService handle a fatal startup dependency failure, such as being unable to connect to a required message queue at launch? How do you safely access scoped services (like a DbContext) from within a BackgroundService, which itself is registered as a singleton? What is IHostedLifecycleService, and how does it provide more granular hooks than IHostedService's StartAsync/StopAsync?
Advertisement
Back to results for “Background Services”
.NET › Background Services

How should exceptions be handled inside a BackgroundService's ExecuteAsync loop to prevent the entire service from crashing silently?

Intermediate

Answer

An unhandled exception escaping ExecuteAsync causes the BackgroundService to stop entirely (and by default, in .NET 6+, can even trigger the whole host to shut down if configured), so production code should wrap individual work iterations in try/catch, log the exception, and continue the loop -- reserving unhandled propagation only for truly fatal, unrecoverable conditions.
protected override async Task ExecuteAsync(CancellationToken stoppingToken) {
    while (!stoppingToken.IsCancellationRequested) {
        try {
            await ProcessBatchAsync();
        } catch (Exception ex) {
            _logger.LogError(ex, "Batch processing failed, will retry next cycle");
        }
        await Task.Delay(TimeSpan.FromSeconds(30), stoppingToken);
    }
}
Real-world example A background service silently stopped processing for three days after an unhandled exception in one iteration terminated the whole loop -- a fix wraps each iteration's work in try/catch so a single bad message no longer takes down the entire background processor.

Common follow-ups: What is the BackgroundServiceExceptionBehavior option added in .NET 6?;How do you get alerted when a background service has stopped unexpectedly?

Logging;Diagnostics & Performance
All 15 Background Services questions