Supervisord get confused two programs in configuration file

I have two laravel 5.1 aplications that uses beanstalkd and supervisord to manage queue jobs.

The supervisord.conf file has the two programs defined as

[program:diagbovespa-default-queue]
command=php artisan queue:listen --tries=2 --env=aceite
process_name=%(program_name)s_%(process_num)02d
directory=/sciere/sites/diagbovespa.aceite.pro.br
numprocs=2
user=apache
redirect_stderr=true
autostart=true
autorestart=true
stdout_logfile=/sciere/sites/http://ift.tt/1Mj2Rdg

[program:questionarioise-default-queue]
command=php artisan queue:listen --tries=2 --env=aceite
process_name=%(program_name)s_%(process_num)02d
directory=/sciere/sites/questionarioise.aceite.pro.br
numprocs=2
user=apache
redirect_stderr=true
autostart=true
autorestart=true
stdout_logfile=/sciere/sites/http://ift.tt/1M32BV6

The queue.php file for diagbovespa application has beanstalkd defined as

    'beanstalkd' => [
        'driver' => 'beanstalkd',
        'host'   => 'localhost',
        'queue'  => 'default',
        'ttr'    => 60,
    ],

and the queue.php questionarioise application has beanstalkd defined as

    'beanstalkd' => [
        'driver' => 'beanstalkd',
        'host'   => 'localhost',
        'queue'  => 'questionarioise',
        'ttr'    => 60,
    ],

So beanstalkd consider two queue groups, default and questionarioise.

The problem is that when I send an email via laravel default queue (program:diagbovespa-default-queue), sometimes I receive email from diagbovespa, sometiems from questionarioise.

What I'm missing in supervisord and/or beanstalkd configuration?

via Chebli Mohamed