People searching “Laravel failed jobs Vue” render the exception column in the page. That text can include request data. Store the failures, and show an admin the safe columns. The queue guide is the happy path.
TL;DR
- queue:failed-table stores the failure.
- An admin page may show the name and the time.
- It does not show the payload.
- Do not put
payloadorexceptionin an Inertia prop.
The fix#
php artisan queue:failed-table
php artisan migrateQUEUE_CONNECTION has to be something that records failures. sync runs the job in the request and does not use this table.
An admin page can pass:
'failed' => DB::table('failed_jobs')->orderByDesc('id')->limit(20)->get(['id', 'uuid', 'failed_at']),Retry from a command you trust, not from a public button:
php artisan queue:retry allWhat to avoid#
Gotcha
Do not put payload or exception in an Inertia prop. Do not let every signed-in user open this list. A failed mail job is not their business unless they administer the app.
FAQ#
How do I show failed jobs to an admin?
queue:failed-table stores the failure. An admin page may show the name and the time. It does not show the payload.
What goes wrong with Laravel failed jobs Vue?
Many developers render the exception column in the page. Do not put payload or exception in an Inertia prop.
