Queues Dashboard

Open a Redis connection to see its queues, job counts, and pause state. Select a queue to inspect jobs or take action. Counts describe current Redis state; use native metrics for throughput trends.

Route Scope

Primary queues overview route:

• /$orgSlug/c/$connectionId/

This route is connection-scoped and aggregates queue-level status data for the selected Redis connection.

For queue-level native telemetry charts and worker metrics setup, see:

• BullMQ Native Metrics

What You See

• Queue summary cards:
  • Waiting
  • Prioritized
  • Active
  • Delayed
  • Completed
  • Failed
• Queue table with per-queue job counts and status (including prioritized)
• Empty state guidance when no BullMQ queues are discovered

Data Source Behavior

Queue discovery is Redis key based:

• Scans for <prefix>:*:meta, using the connection's BullMQ prefix (bull by default)
• Extracts queue names from those meta keys
• Pulls job counts and pause state for each discovered queue

This is why empty results usually indicate either:

• wrong connection
• empty Redis instance
• non-BullMQ workloads only
• a BullMQ prefix or Redis database number that does not match the application

Operational Reading Tips

• High waiting + low active often indicates worker capacity bottlenecks.
• Prioritized counts surface urgent jobs that are processed ahead of the standard waiting set; watch these alongside waiting for at-a-glance triage.
• Rising failed counts should be investigated from queue/job details.
• Delayed growth can be expected for time-based workloads but should be correlated with scheduled jobs and invoke actions.