Download the PHP package kirschbaum-development/laravel-queue-batch-retry without Composer
On this page you can find all versions of the php package kirschbaum-development/laravel-queue-batch-retry. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kirschbaum-development/laravel-queue-batch-retry
More information about kirschbaum-development/laravel-queue-batch-retry
Files in kirschbaum-development/laravel-queue-batch-retry
Package laravel-queue-batch-retry
Short Description Package to retry failed jobs in batch using custom filters
License MIT
Homepage https://github.com/kirschbaum-development/laravel-queue-batch-retry
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-queue-batch-retry
Laravel Queue Batch Retry
Laravel only allows you to retry one job per time or all of them when using the queue:retry command. This package gives you a few more options so you retry failed jobs in batches filtering to only the jobs you want.
Installation
You can install the package via composer:
Usage
There's two different commands this package provides.
queue:failed:batch-retry
--filter
The failed_jobs table is not really a structured table, so "searching" is basically a like condition on the payload condition. Using this option, depending on how many records you have, could be very slow since it will have to do a full table scan to find results. Hopefully, you don't have a lot of failed jobs, though.
--filter-by-exception
Same as the --filter option, but for the exception column in the failed_jobs table. Using this option, depending on how many records you have, could be very slow since it will have to do a full table scan to find results.
--failed-after
This option filters failed_at column. So let's say you had a bunch of jobs that failed today because of some API error in one of the services you use. You can retry all the jobs that failed since "today".
--failed-before
Same as the failed-after, but looking at previous dates.
--limit
In case you want to run in just a specific number of jobs.
--dry-run
We always get afraid of screwing things up, right? You can run dry run the command and see what's going to be executed first.
queue:failed:batch-delete
In case you simply want to clean up your failed jobs table, there's also a queue:failed:batch-delete command which works exactly the same as the queue:failed:batch-retry command. You can use the same filters and options provided by the retry command.
Changelog
Please see CHANGELOG for more information what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security
If you discover any security related issues, please email [email protected] or [email protected] instead of using the issue tracker.
Credits
Sponsorship
Development of this package is sponsored by Kirschbaum Development Group, a developer driven company focused on problem solving, team building, and community. Learn more about us or join us!
License
The MIT License (MIT). Please see License File for more information.
