QueueScope

Frequently asked questions

Straight answers about installing QueueScope, connecting to Redis, and inspecting BullMQ jobs.

Getting started

Is QueueScope free?

Yes. QueueScope is free and open source under the MIT license. The signed Mac app is available from GitHub Releases or our Homebrew tap. No QueueScope account is required.

Which operating systems and BullMQ versions are supported?

QueueScope 0.6.0 requires macOS 14 or later and runs on Apple Silicon and Intel Macs. It targets BullMQ 5.77.x Redis layouts. It is not a Windows or Linux app, and compatibility with every BullMQ version is not guaranteed.

Do I need to install Node or run a dashboard server?

No. The packaged app includes its Node runtime and the official BullMQ package for job actions. You connect from the Mac app to Redis. Building QueueScope from source still requires the build dependencies described in the repository.

Can I try it without connecting to Redis?

Yes. Open Connection Manager and choose Explore offline demo. It contains sample queues, failure groups, and a parent/child flow. All mutations are disabled in the demo. Your saved connection settings stay intact.

Connections and privacy

Where are Redis credentials and queue data stored?

Release builds store Redis credentials in macOS Keychain. Connection metadata and metric snapshots are stored locally. QueueScope does not send queue payloads or Redis credentials to a QueueScope service. Development builds use a separate unencrypted credential store. See our privacy policy for website analytics and update-check details.

Can I connect to Redis on a private network?

Yes, through an SSH tunnel using system OpenSSH and an existing key or SSH agent. The Redis address must be reachable from the SSH server. QueueScope retains known-host checks and Redis TLS verification. Interactive SSH password prompts are not supported. Read the SSH connection guide.

Does a read-only profile prevent job changes?

It prevents QueueScope job mutations, including bulk actions and queue pause/resume. The setting applies to the connected session; editing the form does not change an active session. Use Redis ACLs when you need server-enforced permissions. A read-only profile does not change what other applications can do.

Why is my queue list empty?

Check the Redis database and BullMQ prefix against your producer and worker configuration. Discover queues, then use Scan more if discovery is incomplete. Confirm the Redis credentials permit the required reads. An empty list alone does not mean your application has no jobs.

Debugging jobs

Does Failure inbox scan every queue?

It starts with the selected queue. Enable All queues to group retained failures across discovered and saved queues in the active connection and prefix. Check scan coverage, and use Scan more for partial scans. Switching scope resets the previous scan comparison.

Can QueueScope recover jobs that were removed?

No. The app shows jobs retained in Redis. Jobs removed by BullMQ retention settings or manual deletion cannot be reconstructed by the dashboard. Scan counts are not lifetime failure totals. Read how retention affects debugging.

Can I retry, duplicate, or remove jobs?

Eligible jobs on writable connections have BullMQ-backed actions. QueueScope supports retry, duplicate with editable data/options, delayed-job promotion, and removal of non-active jobs. Eligibility depends on job state and connection permissions; app confirmations still apply. Start with the failed-job investigation guide.

Why does the flow graph say it is partial?

QueueScope bounds each graph to 80 jobs, eight ancestor levels, and six descendant levels. Open a descendant’s flow to explore its branch. Jobs under another prefix can be inspected, but mutations are disabled until you connect to that prefix. See the parent/child debugging article.