Member Since 1 Month Ago
4,910 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Thanks Snapey! Very odd, no problems at all now the code is in the job rather than called as a function of a helper (identical code). I hope at some point diagnosing these becomes easier!
An interesting oddity. This morning I updated the problematic job so that instead of calling a function from a helper, I've copied the code from the helper function and placed it directly in the job. Last test showed no MaxAttemptsExceededExceptions).
I had assumed that a function called from a job would inherit the jobs timeout but maybe not?
I'll need to run a few more tests to confirm its not a fluke result.
Not but there are a lot of DNS requests involved so it can be slow but that said, I'm not getting any errors about the actual lookups timing out (or the script running them).
Thanks Snapey, I've done that but that only shows me what has executed in the job successfully and I never seen any half-finished jobs! I love Laravel but this one error is the bane of my life! :-)
I think the thing that frustrates me the most is the "it may have previously timed out" but if there is no error of it timing out and no execution errors logged (which is always the case when I get a MaxAttemptsExceededException), I don't know how to diagnose the problem.
Started a new Conversation Diagnosing Queue MaxAttemptsExceededException Errors
I'm wondering how other people diagnose MaxAttemptsExceededException errors because it's something I've always struggled with. The main problem being the lack of information, I'm wondering if there is a way to find out for example: A job has been re-attempted but why? What are the parameters passed to this job to help me identify which records it pertains to? The only entry in "failed jobs" says the same as the error log so no additional help there. THe error says "The job may have previously timed out" - how do I know?
In summary, I don't know how to get any information that helps me diagnose the problem!
I'm using Laravel 8 and for my queuing, I'm using AWS SQS.