I locally run the phpartisanqueue: listen -- tries5 queue command and put it into the job (here only outputs simple characters to the log file). It will soon be executed, but after being deployed to the official environment, the task in the job can be consumed after 1 minute. May I ask... I locally run the php artisan queue: listen -- tries = 5 queue command to put it into the job (here only outputs simple characters to the log file) and it will soon be executed, however, after the task is deployed in the formal environment, it can be consumed after 1 minute after it is placed in the job. Have you ever encountered any similar problems? How can this problem be solved?
Reply content:
I locally run the php artisan queue: listen -- tries = 5 queue command to put it into the job (here only outputs simple characters to the log file) and it will soon be executed, however, after the task is deployed in the formal environment, it can be consumed after 1 minute after it is placed in the job. Have you ever encountered any similar problems? How can this problem be solved?
The minimum Cron granularity is 1 minute. Check whether your queue process is written to crontab.