backend-queues

Configure Drumr workflow queues with concurrency, retries, timeouts, and lifecycle hooks.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-queues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-queues
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/backend-queues
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-queues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill explains how Drumr workflow queues control execution behavior instead of acting like generic job queues, helping you avoid incorrect BullMQ-style assumptions while setting the right concurrency, retry, timeout, and isolation rules.

Core Features & Use Cases

  • Queue configuration: Define custom queues with name, concurrency, timeout, retry attempts, backoff, and rate limiting.
  • Lifecycle hooks: Observe workflow active, completed, failed, and progress events for logging, metrics, or notifications.
  • Queue routing: Assign workflow actions, scheduled actions, and individual steps to specific queues and override priority or timeout when needed.
  • Use case: Use a custom report queue for heavy generation jobs, a light queue for API-driven workflows, and built-in queues when the default execution profile is sufficient.

Quick Start

Ask the assistant to create a Drumr queue class with the correct queue configuration, lifecycle hooks, and workflow action routing for your backend task.

Frequently Asked Questions about backend-queues

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

FAQPage Schema
How do I configure workflow queues for backend concurrency and rate limiting?

Workflow queues are configured by defining a custom queue class with specific concurrency, timeout, retry attempts, backoff, and rate limiting parameters. This controls workflow execution behavior precisely rather than acting as a generic job queue.

What is the best way to route scheduled workflow actions to specific queues?

Queue routing assigns workflow actions, scheduled actions, and individual steps to specific custom queues. You can override priority or timeout settings when needed to isolate heavy generation jobs from light API-driven workflows.

Does Drumr workflow queue management work like generic BullMQ-style job queues?

No, Drumr workflow queues control execution behavior instead of acting like generic job-queue APIs. You should avoid BullMQ-style assumptions and rely on BaseQueue, @Queue, WorkflowAction, and ScheduledWorkflowAction for lifecycle management.

How do I monitor workflow queue lifecycle events like active, completed, and failed?

Lifecycle hooks observe workflow active, completed, failed, and progress events. These hooks are defined within custom queue classes to enable logging, metrics collection, or notifications based on execution status.

When should I use custom backend queues instead of built-in queues for workflows?

Use custom queues when you need specific concurrency, retries, timeouts, rate limits, or isolation rules for heavy tasks like report generation. Use built-in queues when the default execution profile is sufficient for your workflow.

Why do I need to avoid manual workers when setting up backend workflow queues?

Manual workers and internal system-only options are bypassed because Drumr workflow queues manage execution behavior natively. The built-in queue model combined with BaseQueue and @Queue handles routing, concurrency, and retries automatically.