Skip to main content
Queue Jobs

See why a queue job failed, attempt by attempt

A SendReport job sends no mail at first. Open it and see three attempts on one time line, about 11 seconds apart: two failed with SMTP connection refused, the third worked. A link leads to /reports/send, the request that queued it. All on your machine, from your Sentry traces.

Set it up Sentry → Queues · sentry-laravel
127.0.0.1:8000
Buggregator job page: ChargeCustomer failed after 3 attempts, dispatched from POST /checkout, three attempts on a time scale with the pauses between them and the exception of each

A job page: three failed attempts with the pauses between them, the exception of each, and the request that queued the job.

Every job your worker ran

Attempts of the same job are put together by the job’s UUID, so a retried job is one row, not three.

❌

Failed, retried or done

Each job’s status is the status of its last attempt: Done, Retried (worked after more than one attempt) or Failed.

🕜

Every attempt on one time line

Attempts as bars with the pauses between them, for example 11 s before a retry. Each with its duration, wait time and exception.

🔗

Dispatched from

A link to the trace of the request that queued the job, for example /reports/send.

📊

Tiles and filters

Jobs, failed, retried and average duration for the period. Filter by queue, or show failed jobs only.

⏱

Waited and ran

How long the job waited in the queue before it started, and how long its last attempt ran.

🤖

API and MCP

The same data at /api/sentry/queues/jobs and /summary, and through the MCP tool queue_jobs for AI agents.

127.0.0.1:8000
Buggregator Queues tab: tiles for jobs, failed, retried and average duration, queue and status filters, and a table of jobs

Sentry → Queues: every job with its status, queue, attempts, duration and when it finished.

The customer says the report never came

Open Sentry → Queues and pick Failed only. SendReport failed after 3 attempts, each with RuntimeException: SMTP connection refused, about 11 seconds apart. Dispatched from leads to the request that queued it. Now you know the job ran, why it failed, and that the retries did not help.

Setup in 60 seconds

No registration. No account. Start it and point your app at it.

1

Start Buggregator

Requires Buggregator v2.14.0 or later. The UI and the Sentry endpoint are both on port 8000. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.

$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh
$ HTTP_ADDR=127.0.0.1:8000 \
  SMTP_ADDR=127.0.0.1:1025 \
  VAR_DUMPER_ADDR=127.0.0.1:9912 \
  MONOLOG_ADDR=127.0.0.1:9913 \
  PROXY_ADDR=127.0.0.1:8080 \
  ~/.local/bin/buggregator

The script picks the file for your CPU: Intel/AMD or ARM.

One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.

This run line keeps it on this computer. Without the *_ADDR settings it listens on all network interfaces

Rather not run a script? Download the file yourself

Runs on Windows, macOS and Linux, on Intel/AMD and ARM.

Prefer not to do it yourself? Your AI agent can set Buggregator up for you

2

Turn on queue job tracing

The Queues tab is built from Sentry traces: sentry-laravel sends one transaction per job attempt. Tested with sentry-laravel 4.31.

SENTRY_LARAVEL_DSN=http://sentry@127.0.0.1:8000/1
SENTRY_TRACES_SAMPLE_RATE=1
SENTRY_TRACE_QUEUE_ENABLED=true
3

Restart the worker and open Sentry → Queues

Run php artisan queue:restart, so the worker reads the new settings. A job shows up when its attempt ends. Before the first job, the page at /sentry/queues shows the same setup steps.

Works with Laravel queues through sentry-laravel

No new package: the Sentry SDK you already use sends the attempts.

Laravel— sentry-laravel with SENTRY_TRACE_QUEUE_ENABLED=true
Any queue driver with a worker— database, redis and others; not sync
Request timeline— jobs a request queued are in its Jobs lane

What it does not do

  • No running jobs: Sentry sends an attempt when it ends.
  • Failed means the last attempt failed. Sentry does not say whether the worker will try again.
  • No job payload: Sentry sends only the job’s class, queue and UUID.
  • Buggregator does not retry jobs. Your worker does; Buggregator shows the attempts.
  • Jobs on the sync driver run inside the request: they are in the request’s timeline, not on this page.

Ready to try it?

One command to start. No account needed.