Queued Jobs

The Queued Jobs resource provides visibility into every job dispatched to your application’s queue system. Use this page to track job status, measure queueing delays, and identify slow or failing background processes.

Navigation: Access Queued Jobs via the sidebar under the “Queued Jobs” section.

---

1. Queued Jobs Index Table

The main content of the Queued Jobs page is a table listing individual job records. By default, the table displays the 25 most recently dispatched jobs, ordered by Dispatched At in descending order. Click Load More at the bottom to load additional records.

1.1 Columns

1. Job

   • The class name or identifier of the job (e.g., SendEmailJob, GenerateReportJob).

2. Dispatched At

   • Timestamp when the job was pushed onto the queue.

3. Processed At

   • Timestamp when the job began execution. If the job is still in the queue or waiting to be picked up, this field may be blank or show a placeholder.

4. Delay (ms)

   • If the job was scheduled to run after a given delay (e.g., dispatch()->delay()), this column shows the delay period in milliseconds. Otherwise, it may show 0 or “—” if no delay was specified.

5. Wait Time (ms)

   • Time the job spent waiting in the queue before starting execution. Calculated as the difference (in milliseconds) between Dispatched At and Processed At.

6. Duration (ms)

   • Total execution time for the job, in milliseconds (i.e., from Processed At until the job completed or failed). If the job is still running, this field may be a placeholder.

7. Status

   • Current state of the job:
     • WAITING: The job is still in the queue and has not started processing.
     • PROCESSED: The job completed successfully (exit code or return value indicated success).
     • FAILED: The job encountered an uncaught exception or returned a failure state.

8. View Icon (👁️)

   • Click to open the Job Details page for this specific job execution (covered in a separate article).

Note: If a job remains in WAITING status for an unusually long period, check queue worker availability and configuration.

---

2. Filters

Above the Queued Jobs table, you can refine the displayed jobs using multiple filter controls. All filters can be combined to narrow down to the jobs you care about.

1. Job Dropdown

   • A dropdown listing all detected job classes or identifiers. Select a job name to filter to only that job type.

2. Date & Time Range

   • Choose a Start Date & Time and End Date & Time to display only jobs dispatched within that window.

3. Duration Filter

   • A numeric input (milliseconds) to filter jobs whose execution time is above or below a specified value.

4. Wait Time Filter

   • A numeric input (milliseconds) to filter jobs based on how long they waited in the queue prior to processing.

5. Status Filter (Badges)

   • Clickable badges for each status (WAITING, PROCESSED, FAILED). Clicking a badge filters to jobs in that state.

Tip: Combine Job + Status filters to quickly isolate all recent GenerateReportJob failures, or use the Wait Time filter to spot jobs experiencing long queue delays.

---

3. Grouping

Next to or above the filter controls, you will find a Group By selector. You can group the job list by either Date or Job. When grouped, the table transforms into an aggregated view that displays summary metrics for each group.

3.1 Group by Date

• Grouping Key: Calendar date (e.g., 2025-05-30).
• Aggregated Columns:
  • Avg. Wait Time (ms): Average queue wait time for all jobs dispatched on this date.
  • Avg. Duration (ms): Average execution time for those jobs.
  • Total Processed: Count of jobs that completed successfully (PROCESSED) on that date.
  • Total Waiting: Count of jobs still in queue (WAITING) that were dispatched on that date.
  • Total Failed: Count of jobs that failed (FAILED) on that date.

Use “Group by Date” to monitor daily queue pressure (e.g., if wait times suddenly spike on a particular day) and observe daily job success/failure rates.

3.2 Group by Job

• Grouping Key: Job class or identifier (e.g., SendEmailJob).
• Aggregated Columns:
  • Avg. Wait Time (ms): Average queue wait time for all instances of this job type.
  • Avg. Duration (ms): Average execution time for those job instances.
  • Total Processed: Count of successful runs for this job type.
  • Total Waiting: Count of job instances still queued.
  • Total Failed: Count of failed runs of this job type.

Use “Group by Job” to pinpoint which job classes are experiencing frequent delays or failures, and compare performance characteristics across different jobs.

---

4. Load More

• The Queued Jobs table initially displays up to 25 entries.
• Click the Load More button at the bottom to fetch the next 25 results, ordered by Dispatched At.
• This incremental loading ensures a fast initial rendering while still giving you access to your entire job history.

---

5. Best Practices

• Spot Stuck Jobs: Use the Wait Time filter to find jobs waiting excessively long in the queue—this often signals worker shortages or misconfiguration.
• Monitor Job Health: Filter by FAILED status to identify and triage job errors quickly.
• Analyze Duration Trends: Use the Duration filter (or group by Job) to discover job types that are gradually slowing down.
• Track Daily Load: Group by Date to monitor daily job volumes, average wait times, and success rates—helpful for capacity planning.
• Investigate High-Delay Jobs: Combine Wait Time + Job filters to isolate specific job classes that frequently experience long queue delays.
• Use Pagination Wisely: If you have thousands of jobs, start by narrowing date ranges or filtering by job class to reduce the number of pages you need to traverse.

By leveraging the Queued Jobs index, filters, grouping, and per-job detail drill-down, you can maintain a clear view of your background processing pipeline, quickly detect bottlenecks, and ensure that all jobs execute reliably and efficiently.