MaxAttemptsExceededException: Job has been attempted too many times or run too long. The job may have previously timed out.

@alex29 but have you restarted the Queue after you changed the job timeout? Maybe it remembers the old value.

You can also set a timeout when you run the queue, using this:

php artisan queue:work --timeout=60

60 is seconds just so you know.

Yes, I have ran sudo supervisorctl reload on my server and it still doesn't work. I might try adjusting my laravel-worker config to include the timeout flag but I wanted to keep it as a class property since I might need to adjust it according to a video file's size.

I hate this error. Tells you nothing on the cause.

I have just came across this issue!

After some Googling, I found out that I didn't specify the timeout for Horizon in its config file(config/horizon.php)

'environments' => [
        'production' => [
            'supervisor' => [
                'connection' => 'redis',
                'queue' => ['default'],
                'balance' => 'simple',
                'processes' => 10,
                'tries' => 1,
                'timeout' => 60 * 60 // <<<<<<<< THIS - timeout in seconds
            ],
        ],

        ....
    ],

That's of course if you are using Horizon.

Hope it could help someone!

Perfect @laracoder , that way it worked for me. I had the timeout set in several places, for example in the "supervisor" service, directly in the configuration file, but same error....

So, i configure directly in configuration file of queues in Laravel ; I leave the code behing, thanks!

    'database' => [
        'driver' => 'database',
        'table' => 'jobs',
        'queue' => 'default',
        'retry_after' => 90,
        'after_commit' => false,
        'timeout' => 180
    ],

Work with issue in complex: nginx, php, laravel, supervisor. Take a look: https://stackoverflow.com/a/76696840/724816