Symfony bundle for PHP Task Manager

1.1.1 2020-10-08 14:52 UTC

This package is auto-updated.

Last update: 2021-04-08 15:51:36 UTC


Build Status

See main repository for base usage

This bundle integrates the task manager to Symfony. Supports Symfony ^3.0 and ^4.0.


composer require sunvalley-technologies/php-task-manager-symfony-bundle

Make sure to add the bundle to your Kernel's bundles.


Complete configuration looks like following:

    task_queue: redis://
    task_storage: redis://
        minimum_processes: 1
        maximum_processes: 10
        time_to_live: 60
        max_jobs_per_process: 10

From which task_queue is the only required configuration parameter.

task_storage is optional and if given is used to store task information.

If you have a non-standard Kernel have a look and replace the SunValley\TaskManager\Symfony\Task\TaskEnvironment class and AbstractSymfonyTask to provide a proper Kernel for your tasks.

Generating and Submitting Tasks

It is necessary to generate tasks to control exactly what each task is doing. This can be thought like generating controllers.

All kernel dependent classes should extend AbstractSymfonyTask and they are synchronous tasks by default.

Here is a sample task that persist a doctrine entity:


class ExampleTask extends \SunValley\TaskManager\Symfony\Task\AbstractSymfonyTask {

    protected function __run(\SunValley\TaskManager\ProgressReporter $reporter,\Symfony\Component\DependencyInjection\ContainerInterface $container){
        $data = $this->getOptions()['data'];
        $entityManager = $container->get('entity_manager');
        $entity = $entityManager->find('\Some\Entity');

        return 'Task Completed'; // will be passed as $result to $reporter->finishTask($result) if it is not called or failed before 

    public function buildOptionsResolver() : \Symfony\Component\OptionsResolver\OptionsResolver{
        $resolver = new Symfony\Component\OptionsResolver\OptionsResolver();
        return $resolver;


class MyService {
    use \Symfony\Component\DependencyInjection\ContainerAwareTrait;

    public function changeDataOnBackground($data) {
        $task = new ExampleTask(uniqid('', true), ['data' => $data]); // this can throw an exception if options are invalid

class MyAsyncService {

    /** @var \SunValley\TaskManager\Symfony\Task\TaskManagerFactory */
    private $taskManagerFactory;

    public function __construct($taskManagerFactory) { $this->taskManagerFactory = $taskManagerFactory; }

    public function changeDataOnBackground($data): \React\Promise\PromiseInterface {
        $task = new ExampleTask(uniqid('', true), ['data' => $data]); // this can throw an exception if options are invalid

        return $this->taskManagerFactory->generate()->submitTask($task);

The call to finishTask or failTask is optional unlike on plain task manager tasks. Any exception that is thrown however is caught and reported back with failTask($error).

To submit a task, the task should be constructed and then it can be submitted with the client as on the example service above.

Task constructors should never block otherwise the main task manager loop can also get blocked.

Starting task manager

Console command task:manager can be used to start the task manager.

In order to attach to your running loops that you also started with Symfony there is a factory for task manager SunValley\TaskManager\Symfony\Task\TaskManagerFactory.

Task manager uses the loop php_task_manager_loop defined in its configuration by default.

Many of these can be changed with a compiler pass in case a customization is necessary.

Other Topics

Doctrine Entity Repository Task

\SunValley\TaskManager\Symfony\Doctrine\EntityRepositoryTask task can be used to offload synchronous doctrine calls to background for async apps. This task does not make sense for usual work queues but can be useful for async apps that partially depend on doctrine for ORM access.