periodic-workers

To set up recurring background jobs for an API host, configure WorkerOptions to customize behavior and register workers using WorkerRegistrationExtensions. This automates scheduling and ensures appsettings alignment for your hosted services.

The best way to manage periodic cleanup tasks in a background service is using a PeriodicWorker base. It provides built-in error isolation and graceful shutdown, preventing common pitfalls during recurring database record retention jobs.

Yes, you can isolate errors and ensure graceful shutdown for periodic tasks. The PeriodicWorker base explicitly focuses on error isolation and graceful shutdown to prevent recurring background jobs from crashing your API host unexpectedly.

You configure WorkerOptions for custom retention and synchronization jobs by defining configuration sections that customize job behavior. This is then aligned with your appsettings during the worker registration process.

You need a hosted service for background processing when your API requires recurring retention, synchronization, or notification jobs. Periodic workers prevent these long-running tasks from blocking standard API endpoint request threads.