Closed electronick86 closed 4 years ago
What is the value of retry_after
in your queue
config file? This should be set to a higher number than the default as well.
@freekmurze, you impressed me one more time 🥇
>>> config("queue.connections.mailcoach-redis")
=> [
"driver" => "redis",
"connection" => "default",
"queue" => "default",
"retry_after" => 660,
"block_for" => null,
]
>>>
This means that the retry after should always be higher than the timeout? In my mind, the retry_after
value was the amount of seconds after a failed job.
This is for sure the cause of #248 .
EDIT : https://laravel.com/docs/8.x/queues#job-expirations-and-timeouts it's now clear.
Hello Guys,
A I mentionned here #248 , I had some trouble a few days ago with a SendCampaignJob that runs multiple times.
I don't have the problem anymore as I create unique index on the
mailcoach_sends
table for (subscriber_id+campaign_id) and that the jobSendCampaignJob
don't attempt several time ( public int $tries = 1; )The project concerned by this issue have two mailing list (217k + 130k subscribers).
The problem is that everytime I send a campaign, I see that the
SendCampaignJob
fails... even if the campaign seems to be send without any issue.I have sent two campaigns today, the problem occurs twice.
Campaign ID 117 created at 06h45 Campaign ID 118 created at 08h30
The errors appears every time about ~11 minutes later.
I have the impression that the Job continues to runs after this errors into the logs as my "sends" continue to be inserted by that jobs after that :
The timeouts in my horizon.php are very high...
Can you help me to understand what happens?