Weave Code
Symfony Scheduled Task Bundle Laravel Package
halloverden/symfony-scheduled-task-bundle
A Symfony bundle for defining and running scheduled tasks using Symfony's scheduler and messenger components, with attribute-based task configuration and a clean integration into your existing Symfony application.
Enables the creation of cron-jobs tasks to be consumed by symfony/messenger
Frequently asked questions about Symfony Scheduled Task Bundle
- Is halloverden/symfony-scheduled-task-bundle a Laravel package?
- No. It is a Symfony bundle that registers through bundles.php and depends on symfony/messenger, symfony/framework-bundle, and Symfony's dependency injection container. None of those primitives exist in a Laravel runtime in a compatible form, so it cannot be installed as a drop-in Laravel package.
- Can I install this bundle in a Laravel application?
- A direct install is not feasible without pulling a Symfony kernel into your app, either as a sidecar Symfony service or through a custom symfony/messenger bridge. That is a substantial architectural commitment for a capability Laravel already ships natively. For a purely Laravel estate, the package is effectively out of scope.
- What is the Laravel equivalent of this bundle's scheduled tasks?
- Use Laravel's native scheduler in app/Console/Kernel.php or routes/console.php with methods such as everyMinute, withoutOverlapping, onOneServer, and runInBackground. Pair each scheduled entry with dispatch(new SomeJob()) onto Redis, SQS, or the database queue. Horizon adds observability over the queued work.
- How do I run a scheduled task exactly once across multiple servers in Laravel?
- Use the onOneServer() method on the schedule entry, backed by a shared cache store such as Redis so the lock is visible to every node. Combine it with withoutOverlapping() to stop concurrent runs on the same node. This mirrors the single-node execution behaviour the Symfony bundle provides, without adding a cross-framework dependency.
- How does Laravel prevent overlapping scheduled task runs?
- Laravel provides withoutOverlapping() on schedule entries, which uses a cache lock to skip a run while the previous one is still executing. For long-running work, runInBackground() plus a suitable lock expiry keeps the scheduler responsive. Overlap suppression and multi-node deduplication are exactly the areas where homegrown schedulers tend to fail.
- Does this bundle support Laravel 10, 11, or 12?
- It does not target Laravel at all, so there is no Laravel version support matrix. Its compatibility surface is Symfony's framework-bundle, messenger, and DI container versions. Checking Laravel version support is the wrong question for this package.
- Is this bundle safe to use in production?
- Adoption risk is high. With five stars, zero dependents, a low composite score around 0.025, and a single maintainer, it shows the signature of a personal project with no security response process and no LTS posture. The bus factor is one, so pinning a production scheduling path to it creates a single point of failure at the dependency layer.
- How would I connect a Symfony scheduler to Laravel queue workers?
- Integrate at the broker level, not the package level. Run the Symfony service that owns this bundle and its schedule, have it publish messages to a shared Redis, SQS, or RabbitMQ queue, and let Laravel workers consume those messages. Keep the coupling at the message contract, and only justify this if a Symfony service already exists in your estate.
- How long does it take to rebuild this bundle's functionality natively in Laravel?
- Roughly one to three engineer-days, including tests. Map each concept one to one: a scheduled task definition becomes Schedule::call(), Schedule::command(), or an invokable job; the message bus payload becomes dispatch(new TaskJob()); and cron parsing is handled by Laravel's cronExpression support on schedule entries. That is materially cheaper than building and maintaining a Symfony bridge.
- What are the best alternatives to this bundle for Laravel developers?
- Use Laravel's native scheduler with queued jobs as the default, optionally with Horizon for monitoring. If your infrastructure already has a scheduler of record such as Kubernetes CronJob or a cloud scheduler, that may replace both this bundle and Laravel's scheduler. The bundle is best treated as a reference design for schedule-to-queue dispatch, not as a dependency to install.
Weaver
How can I help you explore Laravel packages today?