Can you clarify the situation with JobFailed event and failed job logging when the lambda timeout is hit? I accidentally left my timeout at 5 seconds yesterday queue-timeout: 5 and quite a few jobs run (and failed) overnight. Around 2000 jobs failed but only 10 have been captured in the failed_jobs table with Illuminate\Queue\MaxAttemptsExceededException.
If we timeout the Lambda function I am guessing that Larval shuts down and does not have time to record the failure... but then I still seem to get some. All my jobs are set to public $tries = 1 currently so this is not a failure due to retry attempts.
@themsaid I see you have implemented at Laravel\Vapor\VaporJobTimedOutException exception - fast work 😄!
The {Job} has timed out. It will be retried again part; what does this mean exactly? Is this related to the retries parameter on the job? Will the timeout property set on the job also work now?
Thanks. I assume attempts is taken into account also? The exception message is a little confusing as even on the final attempt I think it still says this?