- What is alt-three/retry used for in Laravel?
- alt-three/retry is a Laravel 5 package for retrying failed Artisan console commands through middleware. It is not a general resilience library or a replacement for Laravel's native queue job retry features. Its practical fit is limited to legacy Laravel 5 applications with a confirmed need to retry console commands.
- Is alt-three/retry compatible with Laravel 8, 9, 10, or 11?
- It is not expected to be compatible with modern Laravel versions. The package targets Laravel 5 and likely depends on older illuminate/console contracts and PHP 5.x or 7.x-era constraints. Expect Composer conflicts with Laravel 8+ and PHP 8+, and validate only in a throwaway branch if you must test it.
- How do I install alt-three/retry with Composer?
- You would install it with composer require alt-three/retry only in a legacy Laravel 5 project if the dependency constraints resolve. Pin the version, check its composer.json against your PHP and Laravel versions, and test middleware registration and command lifecycle behavior. Avoid taking a direct dependency on this archived package in any new codebase.
- Does alt-three/retry retry queued jobs?
- The package's reliable scope is Laravel 5 console command retry, not queue job retry. Do not use it as a substitute for Laravel's native queue tries, backoff, job middleware, or Bus::retry features. For queued jobs, native Laravel retry mechanisms are the safer and better-supported option.
- How many retry attempts and delays can I configure with alt-three/retry?
- The package is described as supporting configurable attempts and delays, but it is archived and documentation is limited. Verify the exact options in the source code and test max attempts, backoff behavior, and failure cases before relying on it. It may not provide advanced controls such as jitter, failure classification, or structured observability.
- Is alt-three/retry maintained or safe for production use?
- alt-three/retry is archived, last released in 2018, and has no active upstream maintenance or support path. That creates high lifecycle risk even if the code surface is small. If legacy adoption is unavoidable, fork it privately, scan dependencies, add tests around side effects and retry limits, and document an exit plan.
- What are alternatives to alt-three/retry for retrying Laravel commands?
- For modern Laravel, use native queue or job retry, job middleware, scheduler-level retry behavior, or a small custom console middleware. For legacy Laravel 5, an in-house middleware may be safer than adopting an archived dependency. Treat alt-three/retry as a reference implementation rather than a strategic dependency.
- Can retrying console commands with alt-three/retry cause duplicate side effects?
- Yes, retrying a console command can rerun its logic and duplicate side effects unless the command is idempotent. Commands that write records, send emails, charge payments, or call external APIs need idempotency guards or careful failure classification. You should also log and meter retry attempts so duplicate work can be detected.
- Which Laravel and PHP versions does alt-three/retry support?
- alt-three/retry was built for Laravel 5 and PHP 5.x or 7.x-era dependency constraints. It is not aligned with modern Laravel console middleware APIs or current illuminate packages. Check the package's composer.json and test against your exact Laravel and PHP target before considering it.
- Should I fork alt-three/retry or write my own retry middleware?
- For modern Laravel stacks, prefer native retry primitives or a lightweight custom middleware instead of forking this package. Fork only if a legacy Laravel 5 console-command retry gap is confirmed and your team can own updates. A fork would need updated Composer constraints, private vendoring, tests for idempotency and retry limits, and a documented removal plan.