Queue Dashboard & Job Dispatcher
Interact with Laravel's queue manager. Dispatch jobs with custom failure toggles and delays, track worker statuses, and manage failed job retry pipelines.
Dispatch Custom Job
Architecture & Execution
What is happening
When you dispatch, Laravel serializes the job class properties and saves them as JSON payload in the queue database/Redis. A separate PHP worker process running `queue:work` fetches, hydrates, and executes it asynchronously.
Why it matters
Offloading long operations (e.g. video processing, third-party API hits, transaction confirmations) preserves immediate response times for users, scaling application capacity.
Expected Performance
Redis database handles pop/push in < 1ms, supporting thousands of dispatches per second without locks. MySQL queues work but scale poorly on massive parallel loads.
Trade-offs & Failures
Queued jobs lose HTTP context. Exceptions triggered in background workers write data blocks to the `failed_jobs` table for manual monitoring and replay.
Failed Jobs Log (Top 10)
| ID | Connection / Queue | Class Payload | Exception Snippet | Failed At |
|---|---|---|---|---|