render-background-workers

Configure queue-based background workers on Render with render.yaml blueprints.

Updated May 28, 2026
One-click install
npx skills add https://github.com/render-oss/render-codex-plugin --skill render-background-workers-render-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-background-workers
Source: https://github.com/render-oss/render-codex-plugin/tree/main/skills/render-background-workers
Command: npx skills add https://github.com/render-oss/render-codex-plugin --skill render-background-workers-render-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures and runs queue-based background worker services on Render, enabling asynchronous job processing and graceful shutdown for long-running tasks.

Core Features & Use Cases

  • Supports queue-backed workers across popular frameworks (Celery, Sidekiq, BullMQ, Asynq, Oban)
  • Helps decide among Background Worker, Cron Job, and Workflow patterns for scalable async processing
  • Provides guidance on wiring Key Value (Redis) as a broker and on graceful shutdown with SIGTERM

Quick Start

Configure and deploy a worker service wired to a Redis-backed queue using a render.yaml blueprint, then start the service and verify graceful shutdown behavior.

Frequently Asked Questions about render-background-workers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run background workers on Render for asynchronous job processing?

Background workers on Render run queue-based services for asynchronous job processing using frameworks like Celery, Sidekiq, or BullMQ. You configure the worker, a Redis broker, and a render.yaml blueprint to deploy and verify graceful shutdown behavior.

How do I handle graceful shutdown for long-running tasks on Render?

Graceful shutdown on Render is handled using SIGTERM and configuring maxShutdownDelaySeconds. This ensures long-running tasks in background workers complete or terminate safely before the service shuts down.

When should I use background workers versus cron jobs on Render?

Use background workers for queue-based asynchronous tasks triggered by events, and cron jobs for scheduled tasks. The Skill provides guidance on choosing between workers, cron jobs, and workflows for scalable async processing.

Does Render support Celery, Sidekiq, and BullMQ for queue-based workers?

Yes, Render supports queue-based background workers across popular frameworks including Celery, Sidekiq, BullMQ, Asynq, and Oban. These frameworks connect to a Key Value Redis broker for asynchronous job processing.

What do I need to set up a BullMQ worker on Render?

To set up a BullMQ worker on Render, you need a Render project, a Key Value Redis instance as a broker, and a render.yaml blueprint for worker configuration. This enables asynchronous task processing and graceful shutdown.

Why does my background worker need a Redis broker on Render?

A Redis broker is needed on Render to queue and distribute asynchronous jobs to background workers. The Key Value service acts as the message broker connecting your application to worker frameworks like Celery or Sidekiq.