Render Background Workers

This skill explains worker services on Render: processes that consume jobs from a queue instead of serving HTTP. Pair with render-blueprints, render-env-vars, and render-networking when wiring render.yaml and private connectivity.

When to Use

• Designing or debugging queue-backed workers (Celery, Sidekiq, BullMQ, Asynq, etc.)
• Choosing between a worker, Cron Job, or Workflow for background work
• Configuring Render Key Value as a broker (not a cache) with correct eviction policy
• Implementing graceful shutdown so in-flight jobs are not lost on deploy

Per-framework setup and signal-handling detail: references/queue-framework-setup.md, references/graceful-shutdown.md.

How Workers Work

• Long-running services with no inbound (HTTP) traffic. Render does not expose a public URL or internal hostname for workers the way it does for web or private services—workers cannot receive private network traffic directed at them.