1. Because the setting for the maximum number of seconds a task can execute (timeout) did not take effect in Windows 10, I decided to test this feature on the production Linux server.
2. I added sleep(1200); to the Job’s handle() method. Since $timeout = 600;, I expected the job to fail due to execution timeout.
3. However, after adding it on the Linux server, the change did not take effect.
4. Queue workers are resident processes that keep the started application state in memory. Therefore, they do not notice code changes after starting. So, during your redeployment process, remember to restart your queue workers.
5. You can gracefully restart all queue workers by using the queue:restart command: php artisan queue:restart. See Figure 1.
/var/www/object # php artisan queue:restart
Broadcasting queue restart signal.
6. I executed the queue job again. After the time exceeded 10 minutes, it failed automatically, as expected. See Figure 2.
Modules\\ThemeStoreDB\\Jobs\\ThemeInstallationJob has been attempted too many times or run too long. The job may have previously timed out.