Background jobs stuck but dashboards look healthy
Workers look alive but business tasks silently stop progressing. This often comes from missing progress telemetry, weak liveness checks, and unclear stop/restart rules.
Common symptom variants
Primary playbook
When background jobs hang but workers look healthy and queue pileup grows: why jobs fail silently without timeouts or heartbeats, and the runbook that stops repeat incidents.
Recommended resource
A copy/paste runbook for queue pileups and jobs that run forever: scope, blocker, containment, safe recovery, and prevention guardrails.
Related posts
Requests timing out but CPU normal: thread pool starvation in ASP.NET
When requests time out but CPU is low and restarting fixes it temporarily: how thread pool starvation happens, how to prove queueing, and the smallest fixes that stop repeat incidents.
Requests hang forever: why missing timeouts cause recurring outages in .NET
When requests hang forever and recycling releases stuck work: why missing timeouts create backlog, how to add budgets safely, and the rollout plan that prevents new incidents.