You can use LogBehavior to write logs after each job. Configure example:

'queue' => [
    'class' => \zhuravljov\yii\queue\Queue::class,
    'as log' => \zhuravljov\yii\queue\LogBehavior::class,
],

If you need to exit from listening when throw a new exception use Queue::EVENT_AFTER_ERROR:

'queue' => [
    'class' => \zhuravljov\yii\queue\Queue::class,
    'on afterError' => function (\zhuravljov\yii\queue\ErrorEvent $event) {
        throw $event->error;
    }
],

@zhuravljov
How can exit from listener worker?
After throw an exception wrote error in stdout and don't exit from worker and worker locked! and with below code i can't exit from worker!

'queue' => [
    'class' => \zhuravljov\yii\queue\Queue::class,
    'on afterError' => function (\zhuravljov\yii\queue\ErrorEvent $event) {
        throw $event->error;
    }
],

What can i do?

Beginning from 0.12.0 a job is executed isolatly in a child process. So a job executing doesn't affect on a listener. I will make separate option that would disable this. For example:

php yii queue/listen --isolate=0

What is benefits of isolate listener? when job stuck in worker and locked worker?

Some components are designed for a short life cycle. And they will be broken, if a job is executed in main process, which works in daemon mode for a long time. There are #8 and #12 reports about lost connections of db and mailer components.

Thank you, I waiting for "isolate" option