- How do I install imtigger/laravel-job-status in Laravel?
- Install it with Composer as imtigger/laravel-job-status, then follow the package setup for config and any database migration if you choose database persistence. Add the JobStatus trait to the jobs you want to track and run a real queued job in staging. Because release notes do not state exact Laravel/PHP constraints, verify compatibility in your application before production.
- Which Laravel and PHP versions does imtigger/laravel-job-status support?
- The provided context does not confirm specific Laravel or PHP version constraints for release 1.2.0. Check the package composer.json and README for the authoritative support matrix, and test against your application's Laravel and PHP versions. Treat version compatibility as something to verify in staging rather than assume from the release notes.
- How do I use the JobStatus trait to track a queued job?
- Add the JobStatus trait to a job class, then let the package observe the job lifecycle as it moves through queued, processing, completed, and failed states. You can query the stored status, progress, messages, and errors through the package API. This gives you a per-job status record for UI display and debugging.
- Does laravel-job-status store statuses in cache or database?
- The package can persist job statuses in cache or database according to its configuration. Cache persistence may be simpler but database persistence is more useful when you need durable querying and reporting. If you use the database option, run the required migrations and review indexing for your queue volume.
- How do I show job progress and messages in a Laravel UI?
- Read the stored status, progress, messages, and errors for the job identifier through the package API and render them in your Laravel UI. Refresh or poll that data depending on how live your interface needs to be. Keep the displayed states aligned with the package semantics, especially failed status after retry exhaustion.
- What happens when a Laravel job exhausts retries in laravel-job-status 1.2.0?
- In 1.2.0, retry exhaustion is reflected as a failed status, which is a semantic change from behavior that may have left retries in a non-failed state. Review dashboards, alerts, and workflows that consume statuses so they treat final retry exhaustion correctly. Test the timing of the failed update around the final attempt because the release notes do not specify that detail.
- How does laravel-job-status handle missing or deleted job classes?
- Release 1.2.0 includes a fail-safe for missing job classes, so deleted or renamed classes are handled without breaking status tracking. The notes do not state whether this fail-safe logs, alerts, or silently marks the job failed. Verify it in staging, especially for rollback and blue/green deployments where job classes can disappear.
- Can I extend or customize JobStatusUpdater in laravel-job-status?
- JobStatusUpdater is extensible in 1.2.0, which can reduce the need to fork the package for custom status behavior. Confirm the stable contract for your custom updater and whether it requires service-container binding or subclassing. Add contract tests around your custom updater so package updates do not silently change status transitions.
- What should I test before using laravel-job-status in production?
- Before production, simulate real queue jobs, max-retry exhaustion, deleted or renamed job classes, and worker restarts in staging. Validate dashboards and alerts, then run a limited production rollout while monitoring failed-status volume. At high throughput, assess database write volume and indexing because each status update adds write pressure per job attempt.
- What production failure modes should I monitor when using laravel-job-status?
- Watch for updater exceptions affecting job processing, status drift between the queue backend and package state, max-retry status races, and missing-class fail-safe behavior masking deployment mistakes. Make logs and alerts distinguish retry exhaustion from application failures and from removed job classes. Provide a runbook covering custom updater setup, expected transitions, and rollback steps if 1.2.0 changes dashboard semantics.