You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v3.x of this package, the task handler (TaskHandler.php:98) sets the header X-CloudTasks-TaskExecutionCount as the jobs attempt count. But according to the documentation, the execution count is only incremented when the task was processed, returned a response in time, and the response code is not in the 5xx code range.
In cases where the task execution returns 5xx, the retry count is incremented, but the execution count is not.
Those cases might lead to failed tasks not being stored in the failed jobs table, because the job still has attempts < maxAttempts.
Task not being stored in the failed jobs table can be reproduced by creating a job which simply does
'abort(500)' vs a job that does 'abort(404)'
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
In v3.x of this package, the task handler (TaskHandler.php:98) sets the header X-CloudTasks-TaskExecutionCount as the jobs attempt count. But according to the documentation, the execution count is only incremented when the task was processed, returned a response in time, and the response code is not in the 5xx code range.
In cases where the task execution returns 5xx, the retry count is incremented, but the execution count is not.
Those cases might lead to failed tasks not being stored in the failed jobs table, because the job still has attempts < maxAttempts.
Task not being stored in the failed jobs table can be reproduced by creating a job which simply does
'abort(500)' vs a job that does 'abort(404)'
The text was updated successfully, but these errors were encountered: