Follow queued work beyond the web request

Read the dispatch evidence

The Queue section records bounded lifecycle facts such as the job class, queued or executed kind, connection, queue, job ID, delay, source, duration when available, and failure state.

Use the application call site to answer why the job was dispatched. A job class tells you what can run; the source tells you which request path chose to run it.

Synchronous jobs finish in the same profile

Jobs sent through the synchronous connection run during the current request. Their execution duration and failures belong to that request profile, so compare them with the Timeline and total duration.

Refresh correlated worker activity

New Debug Bar stores queue-worker executions as separate local profiles. Correlation facts can connect a dispatch, queued mail, or queued notification back to the worker profile that sent, completed, or failed it.

If the original profile still shows pending background work, let the local worker process the job and refresh related activity. Open the worker profile for its own queries, logs, exceptions, model writes, mail, notifications, and duration.

Inspect the profile where the failure occurred

A dispatch failure in the web request and a later worker failure are different events. Use the origin profile for dispatch evidence and the worker profile for the exception, attempt facts, logs, and side effects produced while running the job.

Retry attempts can point to more than one worker profile. Compare attempt number, status, exception class, and timing instead of treating the latest attempt as the whole history.

Debug one queued operation

1. 1

   Capture the origin request

   Confirm the job, connection, queue, delay, and dispatch source.
2. 2

   Run the local worker

   Let the same queue process the job under New Debug Bar.
3. 3

   Refresh related activity

   Open the correlated worker profile instead of expecting worker evidence in the web profile.
4. 4

   Inspect the worker cause

   Use Exceptions, Logs, Queries, Models, Mail, and Notifications inside that worker profile.