Horizon Job timeout issue

Same issue here. Could you find a solution?

+1, got exactly the same issue. Works fine on local machine.

Update: I think it goes wrong when running multiple instances of Horizon on a single server. I just removed one instance which I used for site A, and kept the one for site B. Now it works like a charm.

Same problem and not running multiple horizon setups on same server. Added different environments for staging/production also

I usually solve the odd Horizon issue I get with one of the following:

• terminating and then continuing Horizon
• clicking the 'retry' icon next to the failed job
• if that fails, it's most likely down to an error with my job class - errors are sometimes easier to view if you use say the database or sync driver (i.e. not Horizon)

I did get a similar issue where a job kept failing a while ago. This was down to my own error - I was using Horizon for two separate systems, both of which were using the same redis database :/ Setting the correct redis db number for each app resolved that.

The last paragraph was the root cause for me! Thanks @robstar :)

I updated config/database.php by using the appropriate environment variables in my .env, i.e. REDIS_DB and REDIS_CACHE_DB.

    'redis' => [

        'client' => env('REDIS_CLIENT', 'predis'),

        'options' => [
            'cluster' => env('REDIS_CLUSTER', 'predis'),
        ],

        'default' => [
            'host' => env('REDIS_HOST', '127.0.0.1'),
            'password' => env('REDIS_PASSWORD', null),
            'port' => env('REDIS_PORT', 6379),
            'database' => env('REDIS_DB', 0),
        ],

        'cache' => [
            'host' => env('REDIS_HOST', '127.0.0.1'),
            'password' => env('REDIS_PASSWORD', null),
            'port' => env('REDIS_PORT', 6379),
            'database' => env('REDIS_CACHE_DB', 1),
        ],

    ],

Thanks to @datune I learned that Redis allows you to have upto 16 databases by default (remember, this is 0-15, not 1-16!)

Hi folks, could one of you talk through the distinction between the 'timeout' value in the horizon config and the $timeout variable you might set on a job? In my head the 'timeout' value on the horizon config should be larger than the largest $timeout variable on any of my jobs, but I don't really understand the distinction between those two.