Retry one failed Laravel job with a saved Artisan command

Direct answer

Inspect failed jobs with php artisan queue:failed, choose one ID, then retry it with php artisan queue:retry {id}. In LaraBench, save that as an Artisan command template with a {jobId} placeholder. LaraBench asks for the job ID before each run.

When to use this

Use this when the fix is deployed or the failure was caused by a temporary dependency. Do not retry jobs blindly when the underlying exception is still happening.

Terminal approach

php artisan queue:failed
php artisan queue:retry 7

Laravel also supports retrying every failed job, but that should be a deliberate maintenance action:

php artisan queue:retry all

LaraBench approach

• Open Artisan mode.
• Run queue:failed and inspect the failed IDs.
• Create a saved command with a placeholder for the job ID.
• Run the command for one job and review the output.
• Check History before retrying another job.

Command template

queue:retry {jobId}

Name the placeholder jobId and paste the failed job ID each time you run it. The saved command still shows queue:retry before execution.

Expected result

A successful retry command should report that the selected failed job was pushed back onto the queue. The worker still needs to be running, and the job can fail again if the root cause has not been fixed.

Troubleshooting

• If queue:failed is empty, confirm the app uses a failed job provider and that failures are being recorded.
• If the job retries and fails again, inspect the exception before retrying more IDs.
• If nothing processes the retried job, check the queue worker, connection, queue name, and Horizon or supervisor process.

Safety notes

Queue retries change state. They can send emails, charge cards, call APIs, mutate records, or dispatch more work depending on the job. Artisan commands are not automatically safe just because they are repeatable, so prefer staging first and retry one ID at a time in production.

Related workflows

Before retrying production jobs, read the production safety workflow and confirm the selected connection.